nx cloud - exceeding limits #27318
-
I try nx cloud with its hobby plan for the first time, looks really nice! I wonder what happens when the limits are exceeded? Will If its one of these behaviors nx clouds hobby plan is a nice boost at the start of the month for your ci 😃 Anyways, thanks for this nice feature and the free hobby plan! The developer experience by just including one line is really, really incredible! My pipeline looks like this name: ci
on:
pull_request:
concurrency:
group: ${{ github.head_ref }}
cancel-in-progress: true
jobs:
main:
runs-on: ubuntu-latest
permissions:
actions: read
contents: read
steps:
- uses: actions/checkout@v4
with:
fetch-depth: 0
- run: corepack enable
- uses: actions/setup-node@v4
with:
node-version-file: package.json
cache: 'pnpm'
cache-dependency-path: 'pnpm-lock.yaml'
- run: pnpx nx-cloud start-ci-run --distribute-on='4 linux-medium-js' --stop-agents-after='e2e-vite-version-matrix'
- uses: nrwl/nx-set-shas@v4
- run: pnpm i
- run: pnpm nx report
- run: pnpm nx run tools-commitlint:exec:message --value "${{ github.event.pull_request.title }}"
env:
NX_CLOUD_DISTRIBUTED_EXECUTION: false
- run: |
pnpm nx format:check
pnpm nx affected -t lint-eslint test test-vite build e2e-vite-version-matrix --configuration ci
env:
NX_VERBOSE_LOGGING: ${{ runner.debug && true || false }} |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
There is no fallback to a local run.
So some manual workaround is necessary. Or "just" run it locally (the documentation on how to do it is pretty obscure) |
Beta Was this translation helpful? Give feedback.
There is no fallback to a local run.
nx-cloud start-ci-run
falls with non-zero exit and a long ugly stacktracenx affected
steps fail withNX Nx Cloud: Workspace is disabled
So some manual workaround is necessary. Or "just" run it locally (the documentation on how to do it is pretty obscure)