Graphide CI
The always-on agents
What Graphide's agents change to keep your CI fast, all on our end, and how a change is checked before it counts.
Graphide CI keeps getting faster after it starts. Our agents watch every run and keep tuning runners, caches, jobs and slow tests, around the clock, all on our end. There is nothing for you to review or merge.
What they change
- Runners: the size of machine each job gets, and how its tests are split across runners by their timings.
- Caches: dependencies, build outputs and images kept warm, so a job does not rebuild what has not changed.
- Jobs: a slow job split into shards that run side by side.
- Tests: a flaky test quarantined with the runs that show it, and a slow test shortened once a check shows the shorter one catches the same bugs.
How a change is checked
An agent proposes; a check decides. A change is kept only when the check, not the agent, shows it keeps the verdict: every job reaches the same result it did before. A failing test always fails the job, whatever the agents change.
If you want something left alone
Tell us at hello@graphide.com.
Something wrong or missing? Tell us on Discord or at hello@graphide.com.