runJob(Jenkins)
- Karl Henselin
This operation provides an easy way to trigger a Jenkins build and if desired get artifacts from the completed Jenkins build and store them in the FlexDeploy Artifact Repository to use in a FlexDeploy workflow. This operation uses a CI server integration for the Jenkins account information.
CI Server Account Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
Jenkins Username |
| Yes | The user to connect to Jenkins as. |
Jenkins Password |
| Yes | An API token belonging to the Jenkins User. API token is require in place of user’s password for the runJob operation. |
Jenkins URL |
| Yes | The URL of the Jenkins Server (e.g. |
Project Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
Job Name |
| Yes | The name of the Jenkins job to build. |
Inputs
Input Name | Input Code | Required | Description |
|---|---|---|---|
Jenkins Account |
| Yes | Jenkins account with all of the required properties: Jenkins URL, username, and API token. Configure this under Topology - Integrations - CI Server. |
Jenkins Build Parameter JSON |
| No | Valid JSON object used to set any needed parameters for the build. Should be Strings for keys and values, so quote and numbers. e.g. {“key“:”value”, “key2”:”33.43”} |
Artifacts
This operation can produce artifacts that will be stored in the artifacts repository. If consumes is checked, artifacts from the Jenkins build will be retrieved. If not, they will not be retrieved.
Endpoint Selection
This operation will select all available endpoints associated to the Target.
Endpoint Execution
This operation will execute on any one of the selected endpoints and will be random in the determination of which one.
Special Considerations
The build parameters should be Strings for keys and values, so quote and numbers. If you want to set them from project properties, you can add a project property to the workflow and use Groovy to set it on the input.
Related content
- style