Skip to content
Browse files
Merge pull request #49 from jglick/help-JENKINS-50242
[JENKINS-50242] Improved help text to correct a misunderstanding
  • Loading branch information
jglick committed Mar 19, 2018
2 parents aeda5de + 1c2ca93 commit 8a0039503c6b3b394277f67321f8c507cc240d25
Showing 1 changed file with 33 additions and 6 deletions.
@@ -1,13 +1,16 @@
Allows various kinds of credentials (secrets) to be used in idiosyncratic ways.
(Some steps explicitly ask for credentials of a particular kind,
usually as a <code>credentialsId</code> parameter,
in which case this step is unnecessary.)
Each binding will define an environment variable active within the scope of the step.
You can then use them directly from any other steps that expect environment variables to be set:
<pre><code>node {
withCredentials([usernameColonPassword(credentialsId: 'mylogin', variable: 'USERPASS')]) {
sh '''
set +x
curl -u $USERPASS https://private.server/ > output
curl -u "$USERPASS" https://private.server/ > output
@@ -23,13 +26,37 @@
or retrieve values from Groovy code via the <code>env</code> magic variable:
Note the use of <em>single</em> quotes to define the <code>script</code>
(implicit parameter to <code>sh</code>) in Groovy above.
You want the secret to be expanded by the shell as an environment variable.
The following idiom is potentially less secure, as the secret is interpolated by Groovy
and so (for example) typical operating system process listings will accidentally disclose it:
<pre><code>def password = env.PASSWORD</code></pre>
<pre><code>node {
withCredentials([string(credentialsId: 'mytoken', variable: 'TOKEN')]) {
sh /* WRONG! */ """
set +x
curl -H 'Token: $TOKEN' https://some.api/
Note that some steps explicitly ask for credentials of a particular kind,
usually as a <code>credentialsId</code> parameter,
in which case this step is unnecessary.
At least on Linux, environment variables can be obtained by other processes running in the same account,
so you should not run a job which uses secrets on the same node as a job controlled by untrusted parties.
In any event, you should always prefer expansion as environment variables to inclusion in the command,
since Jenkins visualizations such as Blue Ocean will <em>attempt</em> to detect step parameters containing secrets
and refuse to display them.
The secret(s) will be masked (<code>****</code>) in case they are printed to the build log.
This prevents you from <em>accidentally</em> disclosing passwords and the like via the log.
(Bourne shell <code>set +x</code>, or Windows batch <code>@echo off</code>,
blocks secrets from being displayed in echoed commands;
but build tools in debug mode might dump all environment variables to standard output/error,
or poorly designed network clients might display authentication, etc.)
The masking could of course be trivially circumvented;
anyone permitted to configure a job or define Pipeline steps
is assumed to be trusted to use any credentials in scope however they like.
For bindings which store a secret file, beware that

0 comments on commit 8a00395

Please sign in to comment.