Reference global credentials in Bash script in Jenkins job

Question

I created global credentials (username,password) and gave a custom ID. How do I reference this ID in my Bash script? I checked "inject global password" in my job configuration already.

I tried Jenkins: Access global passwords in powershell but doesn't work.

Assume the ID of the global credentials is "USER_PASSWORD", my bash script tried:

echo ${USER_PASSWORD} echo ${env:USER_PASSWORD} 

Doesn't work. I read some online post I would need to query Jenkins API to get the credentials. That doesn't sound right.

Answer 1

Using the Credentials Binding Plugin, global credentials may be injected into the build context. This is done by checking the checkbox labeled Use secret text(s) or file(s) in the Build Environment section of the job's configuration page. Add a Username and password (separated) binding, choose the specific credential you created, and define your username and password variables.

Here's an example of the Credentials Binding Plugin in use, but with a colon-delimited username/password variable instead of the two separate variables:

You can then use the username and/or password variables you defined in your shell script. Assuming a username value of foo and a password value of bar...

Username and password binding, variable name USER_CREDENTIALS:

echo $USER_CREDENTIALS # -> foo:bar 

Username and password (separated) binding, variable names USER_ID and USER_PASSWORD:

echo $USER_ID          # -> foo echo $USER_PASSWORD    # -> bar 

Answer 2

If your credentials ID is "USER_PASSWORD", you have to read it using eg. the following command: USER_CREDENTIALS = credentials('USER_PASSWORD'). After doing this, the username and password are available in the following environment variables: USER_CREDENTIALS_USR and USER_CREDENTIALS_PSW. Jenkins always adds _USR and _PSW endings to the names of the variables.

Example pipeline (I did not fully tested it, but should work):

pipeline {     agent any      environment {         USER_CREDENTIALS = credentials('USER_PASSWORD')     }      stages {         stage('Run') {             steps {                 sh "echo $USER_CREDENTIALS_USR"                 sh "echo $USER_CREDENTIALS_PSW"             }         }     } } 

If you get **** (four asterisks) as output, it's ok - Jenkins automatically masks usernames and passwords in the console output.

More information: https://jenkins.io/doc/book/pipeline/jenkinsfile/#usernames-and-passwords .