Revision history [back]

Confidential text can be transmitted via the options block in a Jenkins pipeline by using the "withCredentials" syntax. This allows you to define a specific credential in the pipeline, such as a username and password or an API token, and pass it securely to your job.

Here's an example:

pipeline {
    agent any
    options {
        withCredentials([usernamePassword(credentialsId: 'my-credentials', passwordVariable: 'PASSWORD', usernameVariable: 'USERNAME')]) {
            // Do something with the credentials
            sh "echo ${USERNAME}:${PASSWORD}"
        }
    }
    stages {
        stage('Build') {
            steps {
                // Build steps
            }
        }
    }
}

In this example, we define the credentials we want to use (in this case, a username and password) using the "withCredentials" syntax within the options block. We then use them later in our pipeline (in this case, using a shell command to echo the username and password) by referencing the variables defined in the "withCredentials" block (in this case, USERNAME and PASSWORD). The sensitive data is encrypted and stored securely in Jenkins.