Skip to content

Commit

Permalink
Merge pull request #121 from xnumad/patch-1
Browse files Browse the repository at this point in the history
README: Make parameters named
  • Loading branch information
jglick committed Oct 12, 2023
2 parents 2239584 + ddb766c commit 1f58ef7
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ The Pipeline Syntax Snippet Generator helps the user generate steps for Jenkins
The recommended approach to pass secret values using the `build` step is to use credentials parameters:

```groovy
build(job: 'foo', parameters: [credentials('parameter-name', 'credentials-id')])
build(job: 'foo', parameters: [credentials(name: 'parameter-name', value: 'credentials-id')])
```

See [the user guide for the Credentials Plugin](https://plugins.jenkins.io/credentials/) for a general overview of how credentials work in Jenkins and how they can be configured, and [the documentation for the Credentials Binding Plugin](https://plugins.jenkins.io/credentials-binding/) for an overview of how to access and use credentials from a Pipeline.
Expand All @@ -25,7 +25,7 @@ The plaintext secret may be persisted as part of the Pipeline's internal state,
Here is an example for reference:

```groovy
build(job: 'foo', parameters: [password('parameter-name', 'secret-value')])
build(job: 'foo', parameters: [password(name: 'parameter-name', value: 'secret-value')])
```

## Version History
Expand Down

0 comments on commit 1f58ef7

Please sign in to comment.