DevOps Pipeline Simulator | mysimulator.uk

CI/CD Pipeline

Commit rate 10 /min

Build parallelism 2 agents

Test flakiness 15%

Throughput

–

Success rate

–

Queue length

–

Deployed

–

How it works

Every commit enters a queue, then advances through Build → Test → Deploy. Build agents work in parallel — only as many commits can build at once as there are agents, so raising the commit rate past what the agents can absorb makes the queue grow. Each commit that reaches Test has a chance to fail based on the flakiness slider; with auto-rollback on, a failed commit is discarded before production and a fresh retry is queued, keeping production green at the cost of throughput. With auto-rollback off, failures still reach the "done" stage but are marked broken.

queue length ≈ λ·W   (Little's Law)
λ = commit rate, W = average time in system
throughput_max = agents / build_time

Commit rate — how often new work arrives; push it past the pipeline's build capacity and the queue backs up visibly.
Build parallelism — number of CI agents building concurrently; more agents drain the queue faster but cost more compute.
Test flakiness — probability a commit fails the test stage regardless of code quality; real flaky tests erode trust in CI and hide genuine regressions.
Auto-rollback — whether a failing commit is safely discarded before deploy (green production, lower throughput) or allowed through to a marked-broken state.

Real-world relevance: this queue-and-agents model is exactly the bottleneck teams hit when a CI system can't keep up with commit volume — the fix is either more parallel build capacity or fewer, more reliable commits per unit time.

Queued Building Testing Deployed Failed

⚠ Couldn't load the 3D engineThree.js failed to load from the CDN. Check your connection and reload.