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

Update buildfarm deployment logic because of groovy v2 changes #147

Open
mikaelarguedas opened this issue Apr 14, 2017 · 2 comments
Open

Comments

@mikaelarguedas
Copy link
Contributor

  • install diffutils from here to /var/lib/jenkins/plugins/groovy/WEB-INF/lib/
  • create a scriptApproval.xml file (referencing all scripts and methods allowed for groovy scripts to run) in /var/lib/jenkins. Content of this file at the time of the writing is here

replaces ros-infrastructure/ros_buildfarm#419

@dirk-thomas
Copy link
Member

Please use the current approval list from Jenkins which has been updated since the creation of the gist (and will continue to be updated).

@nuclearsandwich
Copy link
Contributor

It isn't part of the current xenial refactor, but I think the long term way to handle this will be to write a script which fetches the the current production script approval settings and generates a Groovy script to set the same script approval settings via puppet on newly configured buildfarms.

This will likely need to happen for #42 which is on deck after the migration.

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

3 participants