Create a Jenkins task
With the Release Jenkins task you can run a Jenkins job that is triggered when the task becomes active. The task will complete when the job completes successfully on the Jenkins server; otherwise, the task will fail.
The options for the Jenkins task are:
|Server||The Jenkins server where Release connects. You can configure Jenkins servers in Settings > Shared configuration. You can configure Jenkins servers on a folder level in Design > Configuration tab of the desired folder.|
|Username||Optional user name to use when connecting to the Jenkins server. Use this property to override the user that was configured on the Jenkins server.|
|Password||Optional password to use when connecting to the Jenkins server. Use this property to override the password that was configured on the Jenkins server.|
|Job Name||The name of the job that will be triggered. This job must be configured on the Jenkins server. If the job is located in one or more Jenkins folders, add a
|Job Parameters||If the Jenkins job requires parameters, you can provide them, one parameter per line. The names and values of the parameters are separated by the first
The output properties of the task are Build Number and the Build Status. They can be stored in a variable, for example
In the release flow editor, Jenkins tasks are marked with a blue border.
For more information about using Jenkins with Release, see Using the Release plugin for Jenkins.
Release will schedule the execution of the scripts and poll for the availability of a resource according to a configurable interval. The default poll interval is 5 seconds. You can change this behavior by configuring the interval in the XLRELEASESERVER_HOME/conf/xl-release.conf file. See the configuration options for using scripts.
Note: Changing the default polling interval will affect all custom script tasks, including the Jenkins task.
- [ENG-1481] - Fixed plugin to fetch build status for failed jenkins job