Does this actually run a pipeline?

No. It generates plausible log text only. Step durations are randomized from a seed, and the pass or fail markers are synthetic. Nothing is built, tested, or deployed.

How does the failure mode work?

When you choose Failure and a stage index, that stage is marked failed with an error line, the pipeline aborts, and all later stages are shown as SKIPPED, mirroring how real CI systems short-circuit on a failed step.

What stages are included?

A typical sequence: Checkout, Install dependencies, Lint, Type check, Unit tests, Build, Integration tests, and Deploy. Each carries a short log snippet describing its result.

How is the total duration computed?

It sums the random duration of each stage that ran. If the pipeline aborts on failure, only the durations up to and including the failed stage are counted, just as a real run would report.

CI Pipeline Output Generator

Believable CI logs for demos and tests

CI dashboards, status badges, and DevOps tools all need example pipeline output to render and test against. This tool generates a realistic CI/CD run: ordered stages, per-step timing, pass or fail markers, log snippets, and a final summary line, with the option to inject a failure that aborts the run.

How it works

A seed drives a mulberry32 pseudo-random generator, so the same seed always yields the same durations and layout.

Each stage gets a random duration between roughly 3 seconds and 2 minutes, formatted as m s.
A passing stage shows a check mark, its time, and a snippet such as 214 passed, 0 failed.
If you inject a failure at a stage index, that stage shows a cross, an error line, and every subsequent stage is marked SKIPPED.
The final line reads Pipeline SUCCEEDED in ... or Pipeline FAILED after ....

Tips and notes

Use the success mode for happy-path screenshots and the failure mode to test how your dashboard renders aborted runs and skipped steps. Reuse the same seed in automated tests so your fixtures are deterministic. The stage names follow a common build-test-deploy convention, which makes the output recognizable to most engineers.