Reputation: 9660
I am using the Promoted Builds plugin in Jenkins for deployment of my application into different environments.
I have a manual promotion defined, with a "choice" approval parameter, containing two entries - one corresponding to each of two instances of my application. This generates a drop-down list available at manual promotion time.
The promotion executes a Windows batch script which uses the value from the drop down list to choose what directories to write to, what config files to edit etc.
This works perfectly well - once.
If I want to promote the same build to BOTH environments, I would expect to just be able to execute the promotion twice, choosing each environment in turn from the generated drop down list.
However, when I go to do this, I find that the drop down list has now become a read-only text box that I can't choose the other environment from.
Clearly this is a deliberate design choice - so I would really appreciate some feedback on how best to tackle this problem.
Upvotes: 1
Views: 528
Reputation: 27485
I have 2 promotions for build jobs. Deploy to DEV
and Deploy to QA
.
Yes, you got to do a little more maintenance, because as your number of environments grows, you got to have a promotion job for each. However there are also benefits: each promotion has a different colored star on the build's history, so it's easy to tell just by glancing which builds have been deployed to DEV and which have been deployed to QA.
Update:
If the content of the promotion steps is large, two ways to manage it are:
Upvotes: 2