Configuring CI Using Jenkins and Nx
Below is an example of a Jenkins setup, building and testing only what is affected.
1pipeline {
2 agent none
3 environment {
4 NX_BRANCH = env.BRANCH_NAME.replace('PR-', '')
5 }
6 stages {
7 stage('Pipeline') {
8 parallel {
9 stage('Main') {
10 when {
11 branch 'main'
12 }
13 agent any
14 steps {
15 // This line enables distribution
16 // The "--stop-agents-after" is optional, but allows idle agents to shut down once the "e2e-ci" targets have been requested
17 // sh "npx nx-cloud start-ci-run --distribute-on='3 linux-medium-js' --stop-agents-after='e2e-ci'"
18 sh "npm ci"
19 sh "npx nx-cloud record -- nx format:check"
20 sh "npx nx affected --base=HEAD~1 -t lint test build e2e-ci"
21 }
22 }
23 stage('PR') {
24 when {
25 not { branch 'main' }
26 }
27 agent any
28 steps {
29 // This line enables distribution
30 // The "--stop-agents-after" is optional, but allows idle agents to shut down once the "e2e-ci" targets have been requested
31 // sh "npx nx-cloud start-ci-run --distribute-on='3 linux-medium-js' --stop-agents-after='e2e-ci'"
32 sh "npm ci"
33 sh "npx nx-cloud record -- nx format:check"
34 sh "npx nx affected --base origin/${env.CHANGE_TARGET} -t lint test build e2e-ci"
35 }
36 }
37 }
38 }
39 }
40}
41Get the Commit of the Last Successful Build
Unlike GitHub Actions and CircleCI, you don't have the metadata to help you track the last successful run on main. In the example below, the base is set to HEAD~1 (for push) or branching point (for pull requests), but a more robust solution would be to tag an SHA in the main job once it succeeds and then use this tag as a base. See the nx-tag-successful-ci-run and nx-set-shas (version 1 implements tagging mechanism) repositories for more information.
We also have to set NX_BRANCH explicitly.