We're rolling out updates to Nx Cloud constantly, so we wanted to bring you up to date with what we've been working on lately.
Assignment Rules come out of beta
In your CI pipeline, you've got some tasks of different sizes. Some tasks are quick, like linting or format checking, but you've got more resource-intensive tasks like building apps or running e2e suites. Your smaller tasks can run on a small agent with fewer CPU cores or less memory, but your larger tasks need a larger agent.
But when you're spreading tasks across multiple agents, it's inefficient to increase the size of all the agents to accommodate your larger tasks. So ideally, you have smaller agents for small tasks and larger agents for your larger tasks. But how do you make sure tasks get assigned to the right agent?
Many CI tools have ways of handling this, but we wanted to make things easier. That's why Nx Cloud now has Assignment Rules. This configuration allows you to control which tasks are assigned to certain agents.
Let's take a look at a quick example for Nx Agents:
1# Create five agents using the `linux-medium-js` launch template and five agents using `linux-large-js`
2distribute-on:
3 default: 5 linux-medium-js, 5 linux-large-js
4
5assignment-rules:
6 # for our `app1` projects...
7 - projects:
8 - app1
9 # for targets beginning with "e2e-ci"...
10 targets:
11 - e2e-ci*
12 # and using the `production` configuration
13 configurations:
14 - production
15 # run matching tasks on a `linux-medium-js` agent with parallelism set to 5
16 run-on:
17 - agent: linux-medium-js
18 parallelism: 5
19
20 # for lint and build tasks on any project
21 - targets:
22 - lint
23 - build
24 # run matching tasks on a `linux-large-js` agent with parallelism set to 10
25 run-on:
26 - agent: linux-large-js
27 parallelism: 10
28As you can see, there's a lot of flexibility in the configuration here to fine-tune your agent assignments.
We're so excited about this feature that we've built it to work with both Agents and Manual DTE. So, no matter how you're distributing tasks using Nx Cloud, you can use this new feature! Be sure to check the docs for more details.
We're also providing a new UI that tells you exactly what tasks are being run on which agents and the rules impacting them.
Find your CIPEs with better filtering
Having trouble finding a CI Pipeline Execution (CIPE)? We've added new filter options for the CIPEs list. You can now filter by committer, branch, or date range. You can even sort by duration to help find your longest CIPEs.
Control how flaky task retries work with your workspace
Flaky retries are great at unblocking your CI pipelines by automatically retrying tasks that Nx Cloud detects as flaky. This means you spend less time re-running CI pipelines when you have a task that passes sometimes and fails other times. You now have more control over this process. You can fine-tune how Nx Cloud retries tasks, specify a time range when flakiness is determined, or even turn it off entirely. This helps optimize when tasks are retried so you can control resource use and CI cost.
Request access to protected views
Access control is important, but it can be time-consuming to give the right access to the right people. Now, users can request access with a simple button click, and an admin will be alerted to adjust their access. This automated process saves your team time by not having to send another email or submit a support ticket for access.
Nx Agents supports custom GitHub domains
Using GitHub Enterprise and having a custom URL? Nx Agents now works with these custom domains, check for the option to override your domain during setup.
Not using Nx Cloud yet?Get started now for free!
