How to promote a specific build number from another job in Jenkins?

by

Update as of version 2.23 of Parameterized Trigger Plugin:

With version 2.23+ behavior changed (thanks AbhijeetKamble for pointing out). Any parameter that is being passed by Predefined Parameters section of calling (build) job has to exist in the called (deploy) job. Furthermore, the restrictions of called job’s parameters apply, so if the called job’s parameter is a choice, it has to have all possible values (from promotions) pre-populated. Or just use Text parameter type.

Solution

Yes, I have the exact same setup: a build job (based on SVN commits) and manually executed deploy job. When the user selects any build from the build job (including older builds), they can then go to Promotion Status link and execute various deploy promotions, for example Deploy to DEV, Deploy to QA, etc

Here is how to setup the promotion on build job:

  • You will need these plugins: Parameterized Trigger Plugin, Promoted Builds Plugin
  • You will also need to setup default Archive the Artifacts post-build action on this build job.
  • Check mark Promote builds when
  • Define Name “Deploy to DEV”
  • Under Criteria check mark Only when manually approved
  • Under Actions use Trigger/call builds on other projects
  • In Projects to build enter the name to your deploy job here
  • Check mark Block until the triggered projects finish their builds
  • Mark this build as failure if the triggered build is worse or equal to: FAILURE (adjust according to statuses of your deploy job)
  • Predefined parameters (Code A)

Code A:

Server=IP_of_my_dev_server`  
Job=$PROMOTED_JOB_NAME`  
BuildSelection=<SpecificBuildSelector><buildNumber>$PROMOTED_NUMBER</buildNumber></SpecificBuildSelector>

Above, in the Predefined parameters section, the name to the left of = are the parameters that are defined in your deploy job. And to the right of = are the values that will be assigned to those parameters when this promotion executes. Defines three parameters Server, Job and BuildSelection.

The parameter Server= is my own, as my deploy job can deploy to multiple servers. However if your deploy job is hardcoded to always deploy to a specific location, you won’t need that.

The Job= parameter is required, but the name of the param depends on what you’ve setup in your deploy job (I will explain configuration there). The value $PROMOTED_JOB_NAME has to remain as is. This is an environment variable that the promotion process is aware of and refers back to the name of your build job (the one where promotion process is configured)

The BuildSelection= parameter is required. This whole line has to remain as is. The value passed is $PROMOTED_NUMBER, which once again the promotion is aware of. In your example, it would be #39.

The Block until the triggered projects finish their builds check mark will make the promotion process wait until the deploy job finished. If not, the promotion process will trigger the deployment job and quit with success. Waiting for the deploy job to finish has the benefit that if the deploy job fails, the promotion star will be marked with failure too.

(One little note here: the promotion star will appear successful while the deploy job is running. If there is a deploy failure, it will only change to failure after the deploy job finished. Logical… but can be a bit confusing if you look at the promotion star before the deployment completed)

Here is how to setup deploy job

  • You will need Copy Artifacts plugin
  • Under This build is parameterized
  • Configure a parameter of type Choice (or Text) with name Server (this name has to match with configuration in promotion’s Predefined Parameters in previous section)
  • Choices: Enter list of possible server IPs that would be used by the promotion’s Predefined Parameters in previous section (see update note below)
  • Configure a parameter of type Choice (or Text) with name Job (this name has to match with configuration in promotion’s Predefined Parameters in previous section)
  • Choices: Enter the name of your build job as default. This is only needed if you trigger the deploy job manually. When the deploy job is triggered from promotion, the promotion will supply the value (the Job= from Predefined parameters that we configured). Also, if there is no value passed from promotion’s Predefined parameters, the first choice value will be used. If you have a 1-to-1 relationship between the build and deploy jobs, you can omit the Job= parameter in promotion’s configuration.
  • Update: since version 2.23 of Parameterized Trigger, the available choices in the deploy job configuration have to have all possible values coming from the promotion’s predefined parameters. If you don’t want that limit, use “Text” instead of “Choice”
  • Configure a parameter of type Build selector for Copy Artifact with name: BuildSelection
  • Default Selector: Latest successful build
  • Under Build steps
  • Configure Copy artifacts from another project
  • In Project name enter ${Job}
  • At Which build choose Specified by a build parameter
  • In Parameter Name enter BuildSelection (without ${...}!)
  • Configure the rest accordingly for your artifacts that will be copied from build job to deploy job’s workspace
  • Use the copied artifacts inside the deploy job as you need in order to deploy

So now, with the above deploy job, you can run it manually and select which build number from build job you want to deploy (last build, last successful, by build number, etc). You probably already have it configured very similarly. The promotion on the build job will basically execute the same thing, and supply the build number, based on what promotion was executed.

Let me know if you got any issues with the instructions.

More Related Contents:

  1. CMAKE_BUILD_TYPE is not being used in CMakeLists.txt
  2. How/When does Execute Shell mark a build as failure in Jenkins?
  3. specify project file of a solution using msbuild
  4. How to mark a build unstable in Jenkins when running shell scripts
  5. Gradle buildscript dependencies
  6. How do I make a Jenkins job start after multiple simultaneous upstream jobs succeed?
  7. Lisp Executable
  8. How to store CMake build settings
  9. MSI Build uninstall- Installed directory not removing
  10. What is a build tool?
  11. Go build: “Cannot find package” (even though GOPATH is set)
  12. Copy all files and folders using msbuild
  13. How to read properties file from Jenkins 2.0 pipeline script
  14. CMake output/build directory
  15. Is it possible to create parallel Jenkins Declarative Pipeline stages in a loop?
  16. Multiple dex files define Lorg/apache/cordova/BuildHelper
  17. Xcode keeps building storyboard after each keystroke
  18. How to add a timeout step to Jenkins Pipeline
  19. How to stop an unstoppable zombie job on Jenkins without restarting the server?
  20. Xcode warning: “Multiple build commands for output file”
  21. CMake Error: “add_subdirectory not given a binary directory”
  22. Is there a way to compile a python application into static binary?
  23. Jenkins CI: How to trigger builds on SVN commit
  24. How can a Jenkins user authentication details be “passed” to a script which uses Jenkins API to create jobs?
  25. Is there a way to split/factor out common parts of Gradle build
  26. How do I build a solution programmatically in C#?
  27. Not able to connect adb after upgrate Android Studio to 3.4
  28. IIS 7.5 Fixing An attempt was made to load a program with an incorrect format problem?
  29. Configuring compilers on Apple silicon (Big Sur, Monterey, Ventura) for Rcpp and other tools
  30. Error:Could not initialize class com.android.sdklib.repositoryv2.AndroidSdkHandler

Leave a Comment