Injecting Jenkins Credentials into a Build Job: Difference between revisions
Jump to navigation
Jump to search
| Line 14: | Line 14: | ||
=Pre-Requisite= | =Pre-Requisite= | ||
* | * [[Jenkins_Credentials_Plugin#Overview|Jenkins Credential Plugin]] has to be installed. | ||
* | * [[Jenkins_Credentials_Binding_Plugin#Overview|Jenkins Credentials Binding Plugin]] has to be installed. | ||
Revision as of 19:55, 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-Requisite
- Jenkins Credential Plugin has to be installed.
- Jenkins Credentials Binding Plugin has to be installed.