Puppet cannot be re-run on master without damaging Jenkins configuration. #160
Labels
Comments
This was referenced Jan 19, 2018
nuclearsandwich
added a commit
that referenced
this issue
May 18, 2020
This bumps the forked jenkins module to include a patch I've just done for a change in where the jenkins-cli jar is stored within recent warfiles. I haven't checked how far back this location is present for but with issue #160 outstanding older versions of Jenkins won't ever get this change. This is tested with only Jenkins 2.222.3
This was referenced May 18, 2020
nuclearsandwich
added a commit
that referenced
this issue
Jun 15, 2020
This bumps the forked jenkins module to include a patch I've just done for a change in where the jenkins-cli jar is stored within recent warfiles. I haven't checked how far back this location is present for but with issue #160 outstanding older versions of Jenkins won't ever get this change. This is tested with only Jenkins 2.222.3
|
This issue has been mentioned on ROS Discourse. There might be relevant details there: https://discourse.ros.org/t/work-in-progress-chef-cookbooks-for-ros-build-farm-configuration/16371/1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At the very least, I think this needs some additional documentation.
Right now re-running puppet on master hosts breaks Jenkins in strange ways due to changes in configuration file formats and the removal of additions made after the initial puppet run.
Using either the facilities in the jenkins puppet API as suggested in #31 or some other means to run scripts against the Jenkins master I would like to make it possible to re-run puppet on master without damaging the buildfarm data.
I'm not sure this is something that we'll be able to do all at once but any new changes to the master profile should make every attempt to be idempotent so we can make headway on the existing code without causing new problems.
The text was updated successfully, but these errors were encountered: