Injecting Jenkins Credentials into a Build Job: Difference between revisions
Jump to navigation
Jump to search
Line 26: | Line 26: | ||
Scope: Global. The [[Jenkins_Security_Concepts#Global|Global scope]] is required if the credential must be exposed to the build jobs. | Scope: Global. The [[Jenkins_Security_Concepts#Global|Global scope]] is required if the credential must be exposed to the build jobs. | ||
Username: | |||
Password: | |||
ID: same as username. | |||
OK. |
Revision as of 20:06, 22 May 2018
External
- https://support.cloudbees.com/hc/en-us/articles/203802500-Injecting-Secrets-into-Jenkins-Build-Jobs
- https://support.cloudbees.com/hc/en-us/articles/204897020-Fetch-a-userid-and-password-from-a-Credential-object-in-a-Pipeline-job-
Internal
Overview
This article describes the procedure to declare credentials, in this case an external repository username and password, in a Jenkins credential store and then expose them to a build job, in this case a Gradle-driven build.
Pre-Requisites
- Jenkins Credential Plugin has to be installed.
- Jenkins Credentials Binding Plugin has to be installed.
Procedure
Define the Credential
Credentials -> System -> Global credentials (unrestricted) -> Add Credential
Username with password
Scope: Global. The Global scope is required if the credential must be exposed to the build jobs.
Username:
Password:
ID: same as username.
OK.