Skip to content

Latest commit

 

History

History
190 lines (141 loc) · 8.93 KB

README_PipelineConfiguration.md

File metadata and controls

190 lines (141 loc) · 8.93 KB
Raw

Pipeline setup options

The triggerRemoteJob pipeline step triggers a job on a remote Jenkins. This command is also available in the Jenkins Pipeline Syntax Generator:

You can select a globally configured remote server and only specify a job name here. The full URL is calculated based on the remote server, the authentication is taken from the global configuration. However it is possible to override the Jenkins base URL (or set the full Job URL) and override credentials used for authentication.

Pipeline Syntax Generator

You can also specify the full job URL and use only the authentication from the global configuration or specify the authentication per job.

Pipeline Syntax Generator

Defaults

The simplest way to trigger a job is:

def handle = triggerRemoteJob job: 'https://myjenkins:8080/job/JobWithoutParams'
echo 'Remote Status: ' + handle.getBuildStatus().toString()

If the job has parameters:

def handle = triggerRemoteJob job: 'https://myjenkins:8080/job/JobWithParams', parameters: 'param1=abc\nparam2=xyz'

If authentication is required:

def handle = triggerRemoteJob job: 'https://myjenkins:8080/job/JobWithoutParams', auth: TokenAuth(apiToken: '<theApiToken>', userName: '<userName>')

The pipeline will wait/block until the remote build finished.

Remote Server Configuration

ℹ️ You can configure jobs/pipelines also without any global configuration.

The remote Jenkins server containing the target job(s) can be configured in different ways.

  • Jenkins System Configuration
    Remote servers can be configured in the Jenkins System Configuration and referenced in Pipelines by their name. The server configuration can also include authentication settings.
    triggerRemoteJob remoteJenkinsName: 'remoteJenkins' ...
  • Override Server URL
    On Pipeline level the URL can be set/overridden with parameter remoteJenkinsUrl.
    triggerRemoteJob remoteJenkinsUrl: 'https://myjenkins:8080' ...
    If combined with remoteJenkinsName only the URL of the globally configured server will be overridden, the other settings like authentication will be used from the global configuration.
    triggerRemoteJob remoteJenkinsName: 'remoteJenkins', remoteJenkinsUrl: 'https://myjenkins:8080' ...
  • Full Job URL
    It is also possible to configure the full job URL instead of the job name only and the remote Jenkins server root URL.
    triggerRemoteJob job: 'https://myjenkins:8080/job/MyJob' ...

ℹ️ If the remote Jenkins uses folders please read this.

Authentication

Authentication can be configured globally in the system configuration or set/overridden for each pipeline via the auth parameter.

The following authentication types are available:

  • Token Authentication The specified user id and Jenkins API token is used.
    auth: TokenAuth(apiToken: '<theApiToken>', userName: '<userName>')
  • Bearer Token Authentication The specified token is inserted to a "Authentication: Bearer" header in REST API requests.
    This is useful when the Jenkins deployment is fronted by a token authentication mechanism (such as when running on Red Hat OpenShift)
    auth: BearerTokenAuth(token: '<token>')
  • Credentials Authentication The specified Jenkins Credentials are used. This can be either user/password or user/API Token.
    auth: CredentialsAuth(credentials: '<credentialId>')
  • No Authentication No Authorization header will be sent, independent of the global 'remote host' settings.
    auth: NoneAuth()

Note: Jenkins API Tokens are recommended since, if stolen, they allow access only to a specific Jenkins while user and password typically provide access to many systems.

The Handle Object

The Handle object provides the following methods:

  • String getJobName() returns the remote job name
  • URL getBuildUrl() returns the remote build URL including the build number
  • int getBuildNumber() returns the remote build number
  • RemoteBuildInfo getBuildInfo() return information regarding the current remote build
  • RemoteBuildStatus getBuildStatus() returns the current remote build status
  • Result getBuildResult() return the result of the remote build
  • RemoteBuildStatus updateBuildStatusBlocking() waits for completion and returns the build result
  • RemoteBuildStatus updateBuildStatus() update the handles build status. Required for getBuildInfo() etc. to yield updated results.
  • boolean isFinished() true if the remote build finished
  • boolean isQueued() true if the job is queued but not yet running
  • String toString()
  • Object readJsonFileFromBuildArchive(String filename)
    This is a convenience method to download and parse the specified JSON file (filename or relative path) from the build archive. This mechanism might be used by remote builds to provide return parameters.
def handle = triggerRemoteJob blockBuildUntilComplete: true, ...
def results = handle.readJsonFileFromBuildArchive('build-results.json')
echo results.urlToTestResults //just an example
  • Enum of RemoteBuildStatus may have the values: UNKNOWN, NOT_STARTED, QUEUED, RUNNING, if the remote job did not finish yet.
  • Enum of Result may have the values: ABORTED, FAILURE, NOT_BUILT, SUCCESS, UNSTABLE, if the remote job finished the status reflects the Jenkins build Result.

Blocking vs. Non-Blocking

The triggerRemoteJob command always returns a Handle object. This object can be used to track the status of the remote build (instead of using the environment variables like in the Job case).

There are two ways to use the command, in a blocking way (it will wait/block until the remote job finished) and in a non-blocking way (the handle is returned immediately and the remote status can be checked asynchronously).

Blocking usage (recommended)

The recommended way to trigger jobs is in a blocking way. Set blockBuildUntilComplete: true to let the plugin wait until the remote build finished:

def handle = triggerRemoteJob(
    remoteJenkinsName: 'remoteJenkins',
    job: 'TheJob',
    parameters: 'a=b',
    blockBuildUntilComplete: true,
    ...)
echo 'Remote Status: ' + handle.getBuildStatus().toString()

Non-blocking usage

It is also possible to use it in a non-blocking way. Set blockBuildUntilComplete: false and the plugin directly returns the handle for further tracking the status:

def handle = triggerRemoteJob(
    remoteJenkinsName: 'remoteJenkins',
    job: 'TheJob',
    parameters: 'a=b',
    blockBuildUntilComplete: false,
    ...)
while( !handle.isFinished() ) {
    echo 'Current Status: ' + handle.getBuildStatus().toString();
    sleep 5
    handle.updateBuildStatus()
}
echo handle.getBuildStatus().toString();

Even with blockBuildUntilComplete: false it is possible to wait synchronously until the remote job finished:

def handle = triggerRemoteJob blockBuildUntilComplete: false, ...
def status = handle.updateBuildStatusBlocking()

⚠️ Currently the plugin cannot log to the pipeline log directly if used in non-blocking mode. As workaround you can use handle.lastLog() after each command to get the log entries.

Support of Folders on Remote Jenkins

The Parameterized Remote Trigger plugin also supports the use of folders on the remote Jenkins server, for example if it uses the CloudBees Folders Plugin or the GitHub Branch Source Plugin (formerly GitHub Organization Folder Plugin)

Remote URLs with folders look like this

https://server:8080/job/Folder1/job/Folder2/job/TheJob

Without folders it would only be https://server:8080/job/TheJob

To be able to trigger such jobs you have to either

  1. Specify the full Job URL as Remote Job Name or URL
  2. Specify the job fullname as Remote Job Name or URL + a globally configured Remote Host.
    The jobs fullname in the example above would be 'Folder1/Folder2/TheJob'.