@@ -89,6 +89,14 @@ After the token is generated, create an rc file with the following content:
8989Note: you could use ` ncu-config ` to configure these variables, but it's not
9090recommended to leave your tokens in your command line history.
9191
92+ If you have ` gpg ` installed and setup on your local machine, it is recommended
93+ to store an encrypted version of this file:
94+
95+ ``` console
96+ $ gpg --default-recipient-self --encrypt ~ /.ncurc
97+ $ rm ~ /.ncurc
98+ ```
99+
92100### Setting up Jenkins credentials
93101
94102The ` git-node ` and ` ncu-ci ` commands need to query the Node.js Jenkins API for
@@ -104,8 +112,9 @@ To obtain the Jenkins API token
1041123 . Enter an identifiable name (for example, ` node-core-utils ` ) for this
105113 token in the inbox that appears, and click ` GENERATE ` .
1061144 . Copy the generated token.
107- 5 . Add it into your ` ncurc ` file (` ~/.ncurc ` or ` $XDG_CONFIG_HOME/ncurc ` )
108- with ` jenkins_token ` as key, like this:
115+ 5 . Add it into your ` ncurc ` file (` ~/.ncurc ` or ` $XDG_CONFIG_HOME/ncurc ` , or
116+ ` ~/.ncurc.gpg ` or ` $XDG_CONFIG_HOME/ncurc.gpg ` ) with ` jenkins_token ` as key,
117+ like this:
109118
110119 ``` json
111120 {
@@ -125,6 +134,7 @@ Put the following entries into your
125134```
126135# node-core-utils configuration file
127136.ncurc
137+ .ncurc.gpg
128138# node-core-utils working directory
129139.ncu
130140```
0 commit comments