npm¶
Run NPM script commands in an NVM container with a specified Node version.
Configuration¶
All configs can be set in either the library config or the Application Environment. All configs set in Application Environment take precedence.
Environment variables and secrets set in the library config are concatenated with those set in the Application Environment. Environment variables and secrets with the same key are set to the definition contained in the Application Environment.
Steps¶
Steps are configured dynamically in either the library config or the Application Environment.
libraries {
npm {
[step_name] {
// config fields described below
}
...
}
}
Example Library Configuration¶
Field | Description | Default |
---|---|---|
nvm_container |
The container image to use | nvm:1.0.0 |
node_version |
Node version to run NPM within (installed via NVM) | lts/* |
<step name>.stageName |
stage name displayed in the Jenkins dashboard | N/A |
<step name>.script |
NPM script ran by the step | N/A |
<step name>.scriptArgs |
array of arguments to pass to the NPM script | [] |
<step name>.artifacts |
array of glob patterns for artifacts that should be archived | [] |
<step name>.npmInstall |
NPM install command to run; npm install can be skipped with value "skip" | ci |
<step name>.env |
environment variables to make available to the NPM process; can include key/value pairs and secrets | [] |
<step name>.env.secrets |
text or username/password credentials to make available to the NPM process; must be present and available in Jenkins credential store | [] |
<step name>.useEslintPlugin |
if the Jenkins ESLint Plugin is installed, will run the recordIssues step to send lint results to the plugin dashboard |
false |
<step name>.nvm_container |
The container image to use (if overriding library default) | N/A |
<step name>.node_version |
Node version to run NPM within (if overriding library default) | N/A |
<step name>.git.url |
Git repository to pull and run NPM script from (when different than base job/repository) | N/A |
<step name>.git.cred |
ID of credentials to pull the optional Git repository; must be present and available in Jenkins credential store | N/A |
<step name>.git.branch |
Branch to checkout from optional Git repository | N/A |
Full Configuration Example¶
Each available method has config options that can be specified in the Application Environment or within the library configuration.
application_environments {
dev
prod {
npm {
node_version = "14.16.1"
unit_test {
stageName = "NPM Unit Tests"
script = "full-test-suite"
artifacts = ["coverage/lcov.info"]
npmInstall = "ci"
env {
someKey = "prodValue for tests"
// (1)
secrets{
someTextCredential {
type = "text"
name = "VARIABLE_NAME"
id = "prod-credential-id"
}
someUsernamePasswordCredential {
type = "usernamePassword"
usernameVar = "USER"
passwordVar = "PASS"
id = "prod-credential-id"
}
// (2)
}
}
}
source_build {
stageName = "NPM Source Build"
script = "prod-build"
env {
someKey = "prodValue for builds"
secrets {
someTextCredential {
type = "text"
name = "VARIABLE_NAME"
id = "prod-credential-id"
}
someUsernamePasswordCredential {
type = "usernamePassword"
usernameVar = "USER"
passwordVar = "PASS"
id = "prod-credential-id"
}
}
}
}
}
lint_code {
stageName = "NPM Lint Code"
script = "lint"
artifacts = [
"eslint-report.json",
"eslint-report.html",
"eslint-report.xml",
]
useEslintPlugin = true
env {
someKey = "prodValue for linting"
secrets {
someTextCredential {
type = "text"
name = "VARIABLE_NAME"
id = "prod-credential-id"
}
someUsernamePasswordCredential {
type = "usernamePassword"
usernameVar = "USER"
passwordVar = "PASS"
id = "prod-credential-id"
}
}
}
}
}
}
}
libraries {
npm {
node_version = "lts/*"
unit_test {
stageName = "NPM Unit Tests"
script = "test"
scriptArgs = ["--test=my_tests/unit_test"]
npmInstall = "install"
env {
someKey = "someValue for tests"
// (3)
secrets {
someTextCredential {
type = "text"
name = "VARIABLE_NAME"
id = "some-credential-id"
}
someUsernamePasswordCredential {
type = "usernamePassword"
usernameVar = "USER"
passwordVar = "PASS"
id = "some-credential-id"
}
// (4)
}
}
}
source_build {
stageName = "NPM Source Build"
script = "build"
npmInstall = "skip"
env {
someKey = "someValue for builds"
secrets {
someTextCredential {
type = "text"
name = "VARIABLE_NAME"
id = "some-credential-id"
}
someUsernamePasswordCredential {
type = "usernamePassword"
usernameVar = "USER"
passwordVar = "PASS"
id = "some-credential-id"
}
}
}
}
lint_code {
stageName = "NPM Lint Code"
script = "lint"
npmInstall = "skip"
env {
someKey = "someValue for linting"
secrets {
someTextCredential {
type = "text"
name = "VARIABLE_NAME"
id = "some-credential-id"
}
someUsernamePasswordCredential {
type = "usernamePassword"
usernameVar = "USER"
passwordVar = "PASS"
id = "some-credential-id"
}
}
}
}
end_to_end_tests {
stageName = "Cypress End-to-End Tests"
script = "cy:run"
scriptArgs = ["--env=test", "--test=test_suites/my_tests/validation_test"]
artifacts = ["cypress-results/**/*"]
nvm_container = "nvm-chrome-1.0.0"
git {
url = "https://www.github.com/myaccount/mycypresstestrepo"
cred = "github-pat"
branch = "main"
}
}
}
}
- more envVars as needed
- more secrets as needed
- more envVars as needed
- more secrets as needed
This example shows the prod Application Environment overriding configs set in the library config.
source_build.npmInstall
is preserved as set in library config, since it isn't overridden by the Application Environment.
Minimal Configuration Example¶
The minimal configuration for this library is:
libraries {
npm {
unit_test {
stageName = "NPM Unit Tests"
script = "test"
}
}
}
Secrets¶
There are two types of secrets currently supported: secret text and username/password credentials. These credentials must be stored in the Jenkins credential store and be available to the pipeline.
The name of each credential block (such as someTextCredential
) is arbitrary.
It's just a key, used to supersede library config with Application Environment configs, and when describing configuration errors found by the step.
Dependencies¶
- The SDP library must be loaded inside the
pipeline_config.groovy
file.
Migrating from SDP 3.2 to 4.0¶
SDP 4.0
reworked this library to use dynamic step aliasing.
To recreate the previous source_build()
and unit_test()
functionality of version 3.2
, the below minimal pipeline configuration can be used:
libraries {
npm {
source_build {
stageName = "NPM Source Build"
script = "build"
}
unit_test {
stageName = "NPM Unit Tests"
script = "test"
}
}
}