Overview - Nx

NxWorkspace

CI Pipeline Executions
- Filtered
Runs
Demo

Insights

Compare tasks
Analytics

Sign in

Overview

Nx

Loading workspace stats

Loading workspace insights...

Statistics interval

7 days30 days

Latest CI Pipeline Executions

Filter

Fuzzy

Sort by

© 2026 - Nx Cloud

Terms of Service Privacy Policy Changelog Status Docs Contact Nx Cloud Pricing Company @NxDevTools

NxWorkspace

Agents
Replay
VCS
Self-Healing

Average execution time

28m 50s

815 CI pipeline executions

Computation time saved

188d 14h

Cache hit rate

60%

Time to Green

2h 51m

Was 11h 50m, improved by 76%

Succeeded
23.3.0-beta.2
c32c1cc0 feat(core): cache plugin capabilities so reading them costs at most one load (#36999) ## Current Behavior Some processes load every plugin only to learn what the plugins register: - The affected project-glob locator loads them to read each `createNodes` pattern. - `runPreTasksExecution` and `runPostTasksExecution` load them to check whether any plugin has the hook. With several `nx affected` runs in parallel and the daemon off (common on CI), the graph lock already makes all but one process wait and then read the cached graph. Each waiter still starts the whole set of plugin workers afterwards. Daemon clients do the same in the glob locator, even though the daemon already has the plugins loaded. Separately, reloading plugins (for example after `nx add` changes nx.json) can leave the previous plugin workers running until the daemon restarts (NXC-4966). ## Expected Behavior **The graph carries what its plugins register.** - The process that builds the graph (daemon off) records each plugin's name, `createNodes` pattern and hook flags in the checkout-local database. The rows are stamped with the graph's `computedAt` and written just before the graph. - A process that reads the cached graph answers from the rows with that exact stamp. Any mismatch, missing row or error means "load the plugins", never "no plugin has it". - A process that builds its own graph uses the plugins it loaded. - Daemon clients ask the daemon for its loaded plugins' capabilities (new `GET_PLUGIN_CAPABILITIES` message) instead of loading plugins themselves. - The glob locator only asks when a touched file was deleted. **Plugin workers are owned by one registry.** - Each load declares the plugins it wants before it starts. Plugins no loader wants any more are disposed, including a load that finishes after it was dropped. - A plugin load that fails or times out shuts its worker down. **Graph lock.** `FileLock` gains a non-blocking `tryLock()`. The graph lock takes the lock with it, or waits for the holder with `wait()` and reads its graph. If the holder stopped without writing, it tries to take over, or waits for whoever did. This replaces master's `check()` then blocking `lock()`, which could lose the lock in between and then block the event loop. ## Related Issue(s) Fixes NXC-4966  --- <p><a href="https://app.trypolygraph.com/orgs/6a061dcb561c062131116eca/sessions/cached-plugin-capabilities-b9e56951">View Polygraph session ↗</a></p>  --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com> Co-authored-by: AgentEnder <AgentEnder@users.noreply.github.com> Co-authored-by: FrozenPandaz <jasonjean1993@gmail.com>
by Craigory C...