Injecting Jenkins Credentials into a Build Job: Difference between revisions
Jump to navigation
Jump to search
| Line 9: | Line 9: | ||
=Overview= | =Overview= | ||
This article describes the procedure to declare [[Jenkins_Security_Concepts#Credential|credentials]], in this case an external repository username and password, in a Jenkins [[Jenkins_Security_Concepts#Credentials_Store|credential store]] and then expose them to a build job, in this case a Gradle-driven build. | |||
Revision as of 19:52, 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.