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

Determine where the UID that's appended to Jenkins slave names comes from #85

Open
robled opened this issue Apr 20, 2017 · 1 comment
Open

Comments

@robled
Copy link
Contributor

robled commented Apr 20, 2017

If the Ansible variable jslave_name is set to something like 'cinch-slave', when the Jenkins slave is created it will had a UID of sorts appending to the end of the name, like 'cinch-slave-123fdsa'. We need to find out where this is coming from, and possibly make its existence user-configurable.

@jaypoulz
Copy link

Not to resurrect this from the dead, but I believe the appended ID comes from the java swarm client call.
According to the docs you can pass a -disableClientsUniqueId to disable that feature.

An example of where this gets set is the swarm service template, seen here: https://github.com/RedHatQE/cinch/blob/master/cinch/roles/jenkins_slave/templates/swarm.service#L17. However users can already disable this feature but overriding the ansible variable "jswarm_extra_args", which is set by default here:

Overall this can probably be closed as won't fix. Alternatively, a doc update could address this if this is a FAQ.

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

No branches or pull requests

2 participants