Skip to content
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

Tag slave instances to their jenkins master #310

Merged
merged 5 commits into from
Oct 16, 2018
Merged

Conversation

julienduchesne
Copy link
Contributor

Replaces #274 (from my company)

In the case where you have multiple Jenkins masters using the same configuration (same AMI for multiple clouds), the instance cap is shared between all instances and clouds. The workaround is to add an additional tag with the Jenkins url to have this instance cap unique per Jenkins master.

Copy link
Member

@jvz jvz left a comment

Choose a reason for hiding this comment

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

Looks good to me. Would be nice with tests.

@thoulen thoulen merged commit 68325a9 into master Oct 16, 2018
@julienduchesne julienduchesne deleted the tag-slaves-to-master branch October 17, 2018 01:41
@imod
Copy link
Member

imod commented Oct 26, 2018

@julienduchesne could this be the reason for: https://issues.jenkins-ci.org/browse/JENKINS-54266 ?

@julienduchesne
Copy link
Contributor Author

Seems like it. Using the instance identity's public key would be better indeed IMO

@batmat
Copy link
Member

batmat commented Oct 26, 2018

Fix proposed as #314

@batmat
Copy link
Member

batmat commented Nov 7, 2018

Apart from this, I think it would be great for next times if a JIRA entry can be requested for non trivial changes, so that we can a clear problem definition upstream to refer to.
Here for instance, I think I get it from the PR description, but I am not totally sure. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
6 participants