-
Notifications
You must be signed in to change notification settings - Fork 100
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
Updates for working with newer Jenkins versions #587
Conversation
I've completed a manual sweep of xml template updates resulting from the updated jenkins and plugin versions. Barring the xml version question below this should be all the changes necessary to run on the latest Jenkins LTS with an updated set of plugins. Because of the new publish-over plugin and the added configuration default in parameterized-trigger I am not sure these changes are backwards compatible with a buildfarm_deployment configuration based on master today. Common among all updated configs and is the move to xml 1.1 with the updated XML pseudo tag |
d866c66
to
a583296
Compare
The above comment is still outstanding although it doesn't prevent the buildfarm from operating and I think that can be addressed in a future PR if desired. |
I don't think this package every generates a XML declaration line. So I assume it either gets prepended in the Python library communicating with Jenkins or on the server side. |
3222e93
to
a23797f
Compare
Attempts to wortk with script security plugin 1.48.
These updates are automated based on the plugin version changes and don't take into account structural changes that may occur with configurations.
This construct is used in new configs.
This comes from the 2.35.2 parameterized-trigger plugin. jenkinsci/parameterized-trigger-plugin#95
a23797f
to
084dc6e
Compare
Preserving the development branch for a week to allow others to migrate to master (or a release including this PR). |
Incorporating these changes will require updates to the buildfarm deployment and live Jenkins instance. As I document the process a guide will be available in ros-infrastructure/buildfarm_deployment#207 and the final version will get published to discourse.
Connects to ros-infrastructure/buildfarm_deployment#207