1
- # Private NPM Buildkite Plugin [ ![ Build status] ( https://badge.buildkite.com/705414e5df1533fbc18a2dda1305ec015282575a87edb1e0c1.svg )] ( https://buildkite.com/seek/private-npm-buildkite-plugin )
1
+ # Private NPM Buildkite Plugin
2
+
3
+ [ ![ Build Status] ( https://img.shields.io/endpoint.svg?url=https%3A%2F%2Factions-badge.atrox.dev%2Fseek-oss%2Fprivate-npm-buildkite-plugin%2Fbadge&style=flat )] ( https://actions-badge.atrox.dev/seek-oss/private-npm-buildkite-plugin/goto )
4
+ [ ![ GitHub Release] ( https://img.shields.io/github/release/seek-oss/private-npm-buildkite-plugin.svg )] ( https://github.com/seek-oss/private-npm-buildkite-plugin/releases )
5
+
2
6
3
7
A [ Buildkite plugin] ( https://buildkite.com/docs/agent/v3/plugins ) to allow pipeline steps to easily install
4
8
private packages from an [ npm] ( https://www.npmjs.com ) repository.
@@ -13,7 +17,7 @@ To read the value from an environment variable named `MY_TOKEN` when the plugin
13
17
steps :
14
18
- command : yarn install
15
19
plugins :
16
- - seek-oss/private-npm#v1.1.1 :
20
+ - seek-oss/private-npm#v1.1.2 :
17
21
env : " MY_TOKEN"
18
22
` ` `
19
23
@@ -23,7 +27,7 @@ To read the value from a file named `my_token_file`, use the `file` field.
23
27
steps:
24
28
- command: yarn install
25
29
plugins:
26
- - seek-oss/private-npm#v1.1.1 :
30
+ - seek-oss/private-npm#v1.1.2 :
27
31
file: "my_token_file"
28
32
` ` `
29
33
@@ -35,7 +39,7 @@ approach is discoraged in favour of using with the `env` or `file` fields. This
35
39
steps:
36
40
- command: yarn install
37
41
plugins:
38
- - seek-oss/private-npm#v1.1.1 :
42
+ - seek-oss/private-npm#v1.1.2 :
39
43
token: ${MY_TOKEN}
40
44
` ` `
41
45
@@ -46,7 +50,7 @@ You can also specify a custom npm registry if you are using your own mirror.
46
50
steps:
47
51
- command: yarn install
48
52
plugins:
49
- - seek-oss/private-npm#v1.1.1 :
53
+ - seek-oss/private-npm#v1.1.2 :
50
54
env: "MY_TOKEN"
51
55
registry: //myprivatenpm.com/
52
56
` ` `
@@ -62,6 +66,9 @@ The value of the NPM token will be read from the agent environment when the plug
62
66
around cases where eager binding of variables in `pipeline.yml` means some variables are not present in the
63
67
environment when the configuration file is parsed.
64
68
69
+ > **NOTE** : Beware of using `NPM_TOKEN` as the name for the environment variable. When using that name the variable
70
+ > is unstable and has a tedency to return an empty string in the context of this plugin.
71
+
65
72
# ## `file` (optional)
66
73
67
74
The value of the NPM token will be read from a file on the agent when the plugin executes. This is useful when working
0 commit comments