$12k a year saved with vx vs Nx Cloud
$12k a year saved with vx vs Nx Cloud
vx's CI is one run spread over its own Linux and Mac runners. On Nx Cloud's Team plan with Nx's agents, the same CI would cost about $12,192 a year. On vx it costs $0.
// the vx blog
Posts tagged plugins.
$12k a year saved with vx vs Nx Cloud
vx's CI is one run spread over its own Linux and Mac runners. On Nx Cloud's Team plan with Nx's agents, the same CI would cost about $12,192 a year. On vx it costs $0.
A scheduler that learns from your runs
@vzn/vx-history starts the longest chain first and keeps memory-hungry tasks apart, using times and memory from your past runs.
Extend vx in an afternoon
One command scaffolds a working plugin and its test. Bring your own remote cache through one small interface, hook setup and teardown around the run, or drive vx from your own scripts with run() and planRun().
Your run, on GitHub
Add one plugin line and every vx run shows up on GitHub: a job summary with failures first.
A lockfile bump rebuilds only what it reaches
Core keys no lockfile, and folding the whole file into every key would make one bump rebuild everything. @vzn/vx-lockfile keys each task on its own project's dependencies, so an astro bump here rebuilds 8 of 151 tasks.
A plugin fills one stage, often in under 25 lines
vx is a pipeline with a named hook at every stage. A plugin fills only the stage it needs, and most example plugins are under 25 lines.
Running here is not a plugin
Your machine is always the last place a task can run, and the local cache is always asked first. A dead remote never breaks a build.
Observability that cannot break a run
A broken telemetry plugin costs a warning, never a red build. A sink that throws is turned off for the run, and one that hangs is cut off after 3 seconds.
Run tasks on a remote worker pool, keep the scheduler local
@vzn/vx-reapi runs tasks on any Bazel Remote Execution API worker pool. The graph, the placement decision, retries, timeouts and the cache all stay on your machine; what moves is one self-contained action per task.
Give your coding agent the build's memory
Your coding agent asks what you ask: what can I run, why did that re-run, which tasks flake. vx answers each as JSON from the CLI.