Closed rtamalin closed 4 years ago
What is needed for this to loose the do-not-merge-label?
What is needed for this to loose the do-not-merge-label?
I need to validate for Crowbar runs to ensure that the changes made haven't broken anything there.
I have been using this branch as the basis for the https://ci.suse.de/job/openstack-ardana-fergal/ test job , which I have been using to validate Ardana upgrade testing and repeatedly rebasing it on top of separable patches as I identify them.
I think I'm close to being ready to merge this. ;-)
https://ci.suse.de/blue/organizations/jenkins/openstack-crowbar/detail/openstack-crowbar/1008/pipeline passed so I don't believe I have broken anything in crowbar builds, and the ardana builds have been working for me for weeks.
Add support for being able to build Gerrit test patches for the deploy, update and upgrade phases, rather than just the initial deploy phase.
To support this we add the following additional job paramaters:
Similarly there are two new job parameters that can be used to specify extra repos to be added to the deployer during the update or upgrade phases:
These repos will be leveraged to inject the results of the relevent update or upgrade gerrit package builds into the deployer served repos at the appropriate stage.
Update the Jenkins job, template and Jenkinsfile definitions to define the new job parameters and leverage them at the appropriate stages in the Jenings jobs.
Update the manual mode lib.sh with equivalent support for using the new parameters, which have also been added to the input.yml.example.