nx-cloud CLI

npx nx-cloud login

To provision a local personal access token to access Nx Cloud features run npx nx-cloud login. This will open your browser to the Nx Cloud application and after signing in will generate a personal access token and save it in a configuration file locally called nxcloud.ini.

The format of this file is as follows:

If you have access to multiple instances of the Nx Cloud application (e.g. self-hosted Enterprise and our managed instance), each instance will be saved to this file under its URL.

Our managed instance at https://cloud.nx.app is the default. To provision a personal access token from an alternative instance of Nx Cloud pass the URL as a positional parameter, e.g.

npx nx-cloud logout

To revoke a personal access token from your local environment, run npx nx-cloud logout. This will remove the personal access token from the locally initialized configuration file and also invalidate the token from the Nx Cloud application. You will be prompted to remove a single token or all tokens from your local environment.

npx nx-cloud configure

To provision more than one personal access token for multiple contexts (e.g. home and work machines) you can use the personal access tokens page under your Nx Cloud profile. To save a personal access token to your local nxcloud.ini file without needing to edit the file yourself call nx-cloud configure like this:

To configure multiple tokens for different instances of the Nx Cloud app, you can pass the URL as follows:

npx nx-cloud convert-to-nx-cloud-id

When logging into Nx Cloud with a Personal Access Token, your nx.json file needs to include the nxCloudId property, which acts as a unique identifier for your workspace. If you have been using the previous nxCloudAccessToken to connect, simply run npx nx-cloud convert-to-nx-cloud-id to automatically update your configuration to use nxCloudId.

If you are connecting to Nx Cloud with a workspace that is version 19.6 or lower, this command will also install the latest version of the Nx Cloud npm package and add it into your package.json. Only Nx versions 19.7 and higher natively support the nxCloudId property in the nx.json file; for versions 19.6 and lower, the Nx Cloud npm package will be needed to use that property.

npx nx-cloud start-ci-run

At the beginning of your main job, invoke npx nx-cloud start-ci-run. This tells Nx Cloud that the following series of command correspond to the same CI run.

You can configure your CI run by passing the following flags:

--distribute-on

Tells Nx Cloud how many agents to use (and what launch templates to use) to distribute tasks. E.g., npx nx-cloud start-ci-run --distribute-on="8 linux-medium-js" will distribute CI using 8 agents that are initialized using the linux-medium-js launch template.

You can use different types of launch templates as follows: npx nx-cloud start-ci-run --distribute-on="3 linux-medium-js, 3 linux-large-js".

You can also define the configuration in a file and reference it as follows: npx nx-cloud start-ci-run --distribute-on=".nx/workflows/dynamic-changesets.yaml".

--require-explicit-completion

By default, Nx Cloud will monitor the main CI job and once that completes it will complete the associated CIPE object on the Nx Cloud side. You can disable this by passing --require-explicit-completion. In this case, you will have to add npx nx-cloud complete-ci-run.

--stop-agents-after

By default, Nx Cloud won't terminate any agents until you invoke npx nx-cloud stop-all-agents because Nx Cloud doesn't know if you will need agents to run another command. This can result in agents being idle at the end of a CI run.

You can fix it by telling Nx Cloud that it can terminate agents after it sees a certain target: npx nx-cloud start-ci-run --stop-agents-after=e2e.

The target name for --stop-agents-after should be the last target run within your pipeline. If not, Nx Cloud will end the CI pipeline execution, preventing the subsequent commands from running.

Incorrect example:

If build tasks are all cached, then all build tasks will complete immediately causing lint and test tasks to fail with an error saying the CI pipeline execution has already been completed. Instead you should re-order your targets to make sure the build target is last.

Corrected example:

--stop-agents-on-failure

By default, a failure in one of the commands is going to terminate the whole CI run and will stop all the agents. You can disable this as follows: npx nx-cloud start-ci-run --stop-agents-on-failure=false.

--use-dte-by-default

By default, invoking npx nx-cloud start-ci-run will configure Nx to distribute all commands by default. You can disable this as follows: npx nx-cloud start-ci-run --use-dte-by-default=false.

--with-env-vars (Nx Agents Only)

By default, invoking npx nx-cloud start-ci-run will take all environment variables prefixed with NX_ and send them over to Nx Agents. This means that your access token, verbose logging configuration and other Nx-related environment variables will be the same on your main CI jobs and the Nx Agent machines.

If you want to pass other environment variables from the main job to Nx Agents, you can do it as follows: --with-env-vars="VAR1,VAR2". This will set VAR1 and VAR2 on Nx Agents to the same values set on the main job before any steps run.

You can also pass --with-env-vars="auto" which will filter out all OS-specific environment variables and pass the rest to Nx Agents.

Note: none of the values passed to Nx Agents are stored by Nx Cloud.

Enabling/Disabling Distribution

Invoking npx nx-cloud start-ci-run will tell Nx to distribute by default. You can enable/disable distribution for individual commands as follows:

npx nx-cloud stop-all-agents

Same as npx nx-cloud complete-ci-run.

This command tells Nx Cloud to terminate all agents associated with this CI pipeline execution. Invoking this command is not needed anymore. New versions of Nx Cloud can track when the main job terminates and terminate associated agents automatically.