-
Notifications
You must be signed in to change notification settings - Fork 697
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove cloudId and use the name entered by the user directly. #827
Conversation
This makes the plugin compatible with cloud copy feature that is being introduced in Jenkins core
Originally added for JENKINS-15081 in 9095d31. Did you check that this doesn't reopen (from a Jira comment) this issue?
(Might be specific to the current config UI and obsolete with your core change, but in case anyone would use old core/new plugin.) |
JENKINS-15081 seems to predate the ability to provide a custom name for the EC2Cloud, which was the problem in their case (the cloud name was only computed based on the region, so if you had 2 EC2Cloud instances targetting the same region, they would mix up because of using the same name) |
Reported as JENKINS-70987 @Vlatombe , I am running Jenkins 2.387.1 (latest LTS). When I upgraded the When we reverted back to 2.0.6, the problem went away, so this looks like a bug introduced in 2.0.7. The Jenkins job log shows this:
|
I'm guessing this is the PR that causes the issue. After an upgrade does removing and re-adding the cloud resolve the issue? |
Yes, that did fix the problem. Specifically, I did the following:
|
|
This makes the plugin compatible with cloud copy feature that is being introduced in Jenkins core, cf. jenkinsci/jenkins#7658