From 7754c0cb84ddf5072f3d892a17bb9807c6a952f9 Mon Sep 17 00:00:00 2001 From: Louie Weng <56288712+lourw@users.noreply.github.com> Date: Thu, 16 May 2024 11:42:06 -0700 Subject: [PATCH] docs(nx-cloud): update start-ci-run docs with --force flag and cleanup command (#23168) ## Current Behavior Updates docs to include `nx-cloud cleanup` command as an alternative to resetting your system after running `nx-cloud start-ci-run`. Also provides more context about `nx-cloud start-ci-run`'s check for local environments and how to bypass this check with the `--force` flag. ## Expected Behavior ## Related Issue(s) Fixes # (cherry picked from commit 22d7ea21cce5d3582baca1cac6d9dd1ae258be57) --- docs/nx-cloud/reference/nx-cloud-cli.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/nx-cloud/reference/nx-cloud-cli.md b/docs/nx-cloud/reference/nx-cloud-cli.md index 954723b0abfcd..671e5bb9d1ffe 100644 --- a/docs/nx-cloud/reference/nx-cloud-cli.md +++ b/docs/nx-cloud/reference/nx-cloud-cli.md @@ -6,9 +6,10 @@ At the beginning of your main job, invoke `npx nx-cloud start-ci-run`. This tell command correspond to the same CI run. {% callout type="warning" title="Do not run start-ci-run locally" %} -`nx-cloud start-ci-run` is designed to run in CI. If you run the command locally, it can cause your local Nx repo to think it's a part of a CI run. This can cause strange behavior like Nx commands timing out or throwing unexpected errors. +`nx-cloud start-ci-run` generates a temporary marker file that can cause a local Nx repo to behave as if it is a part of a CI run. This can cause strange behavior like Nx commands timing out or throwing unexpected errors. +To discourage this from happening, this command will run a check to see if it is running in a CI environment. You can bypass this check with `nx-cloud start-ci-run --force`. -If you accidentally run the command locally, you can remove your system's temp files to reset your local system. Typically restarting your system is enough to fix this issue. +If you accidentally run this command locally, remove all generated marker files with `nx-cloud cleanup`. {% /callout %} You can configure your CI run by passing the following flags: