Configuring CI Using Azure Pipelines and Nx

Nx is a smart and extensible build framework, and it works really well with monorepos. Monorepos provide a lot of advantages:

  • Everything at that current commit works together. Changes can be verified across all affected parts of the organization.
  • Easy to split code into composable modules
  • Easier dependency management
  • One toolchain setup
  • Code editors and IDEs are "workspace" aware
  • Consistent developer experience
  • And more ...

But they come with their own technical challenges. The more code you add into your repository, the slower the CI gets. Adding Nx to your CI pipeline makes this more efficient.

Setting up Azure Pipelines

Below is an example of an Azure Pipelines setup for an Nx workspace only building and testing what is affected.

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, but a more robust solution would be to tag a 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 repos for more information.

We also have to set NX_BRANCH explicitly.

1trigger:
2  - main
3pr:
4  - main
5
6variables:
7  ${{ if eq(variables['Build.SourceBranchName'], 'main') }}:
8    NX_BRANCH: 'main'
9  ${{ if ne(variables['Build.SourceBranchName'], 'main') }}:
10    NX_BRANCH: $(System.PullRequest.PullRequestNumber)
11
12jobs:
13  - job: main
14    pool:
15      vmImage: 'ubuntu-latest'
16    condition: ne(variables['Build.Reason'], 'PullRequest'))
17    steps:
18      - script: npm i
19      - script: npx nx affected --base=HEAD~1 --target=build --parallel --max-parallel=3
20      - script: npx nx affected --base=HEAD~1 --target=test --parallel --max-parallel=2
21
22  - job: pr
23    pool:
24      vmImage: 'ubuntu-latest'
25    condition: eq(variables['Build.Reason'], 'PullRequest'))
26    steps:
27      - script: npm i
28      - script: npx nx affected --target=build --parallel --max-parallel=3
29      - script: npx nx affected --target=test --parallel --max-parallel=2

The pr and main jobs implement the CI workflow.

Distributed CI with Nx Cloud

A computation cache is created on your local machine to make the developer experience faster. This allows you to not waste time re-building, re-testing, re-linting, or any number of other actions you might take on code that hasn't changed. Because the cache is stored locally, you are the only member of your team that can take advantage of these instant commands. You can manage and share this cache manually.

Nx Cloud allows this cache to be shared across your entire organization, meaning that any cacheable operation completed on your workspace only needs to be run once. Nx Cloud also allows you to distribute your CI across multiple machines to make sure the CI is fast even for very large repos.

Learn more about configuring your CI environment using Nx Cloud with Distributed Caching and Distributed Task Execution in the Nx Cloud docs.