Skip to content

[JENKINS-25588] - Migrate vSphereCloud to Credentials plugin#16

Merged
jswager merged 1 commit intojenkinsci:masterfrom
oleg-nenashev:JENKINS-25588
Dec 24, 2014
Merged

[JENKINS-25588] - Migrate vSphereCloud to Credentials plugin#16
jswager merged 1 commit intojenkinsci:masterfrom
oleg-nenashev:JENKINS-25588

Conversation

@oleg-nenashev
Copy link
Copy Markdown
Member

Warning! This is a breaking change. A new major version (or a significant modification) are required

Signed-off-by: Oleg Nenashev o.v.nenashev@gmail.com

Signed-off-by: Oleg Nenashev <o.v.nenashev@gmail.com>
@oleg-nenashev oleg-nenashev added this to the 2.0 milestone Nov 14, 2014
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure what these fields do. They seem to be a legacy stuff

oleg-nenashev referenced this pull request in chrislondon/jenkins-gtmetrix-plugin Nov 24, 2014
@jswager
Copy link
Copy Markdown
Member

jswager commented Dec 24, 2014

My apologies - the email notifying of this pull request got routed to my spam folder.

This change looks good. Like you mention, it will require a major upgrade due to the change in credentials.

jswager added a commit that referenced this pull request Dec 24, 2014
[JENKINS-25588] - Migrate vSphereCloud to Credentials plugin
@jswager jswager merged commit aca23f6 into jenkinsci:master Dec 24, 2014
@chris5287
Copy link
Copy Markdown

I've just updated to 2.0 plugin but I cannot figure out how to setup the credential store correctly. No matter what I try I get "Username is not specified" when testing the connection, and any VM slave I try to start returns the following errors:
[JENKINS-...] Starting Virtual Machine...
[JENKINS-...] EXCEPTION while starting VM
[JENKINS-...] java.net.MalformedURLException: no protocol: null/sdk

@jswager
Copy link
Copy Markdown
Member

jswager commented Jan 5, 2015

My initial test of this pull request SEEMED to have worked, but when re-ran the tests - i'm getting the same error.

@oleg-nenashev Can you confirm the behavior described here? And if so, do you know how to resolve it?

@oleg-nenashev
Copy link
Copy Markdown
Member Author

Fixed the validation handler.
I'm working on the second issue. As I remember, the connection worked for me, but it definitely makes sense to re-check it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants