// the vx blog
Posts tagged ci.
ExecutionDTE workers that fit the work, and a footer that says how full they ran
vx DTE puts each task on a machine type that can run it, books it by its measured memory peak and CPU, stops a server once nothing needs it, and prints how busy every worker was.
ExecutionA DTE relay that stores nothing
vx DTE's relay keeps no message, no timer and no storage row. It passes frames between sockets, and the two ends make sure each one lands.
Execution$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.
CachingBranch caches a server enforces
A pull request reads what main built and can never write where main reads. The CI token decides writes, one header steers reads. How it works, and how a cache server builds its half.
PerformanceCarry the scheduler's memory between CI runners
A fresh CI runner has no run history, so it can't know which tasks are slow. One JSON file carries the learned times from runner to runner.
DXThe basics, done carefully
vx run picks the project you are in, never waits on a picker in a pipe, and gives each task its own fold on GitHub Actions.
telemetryWatch a CI run while it runs
@vzn/vx-otel sends each task's span the moment it ends, so your dashboard follows the build live, for the same CPU as one send at the end.
DXOutput that fits the run
One task shows all its output. Many tasks show one line each for what ran. CI shows everything. You can always pick.
CachingThe cache on your terms
Turn the cache off, refresh it, or read one layer and write another. Every clone shares one store, and a pull request never writes what main reads.
PluginsYour run, on GitHub
Add one plugin line and every vx run shows up on GitHub: a job summary with failures first.
DXRun only what a change reaches
vx run test --affected runs what your branch changed and everything downstream of it, and says why each task was picked.
configvx lock: run configs once, check them in CI
vx lock runs every config once and saves the result. Every run reads it, and vx lock --check catches drift a file hash can't see.
