On time or it's free

The CI Runner & Pipeline Setup

Build machines wired into the git platform you already run, with up to three pipelines handed over running green on your own code.

Releases depend on one developer running the build on their laptop. Tests get skipped when deadlines bite, and nobody knows exactly what shipped.

First we run your build and test commands on the build machine, so you know on day one whether they work. We then attach up to two runners to your Git platform and write three pipelines that pass on your real code, plus one deploy step to a server or registry you own.

We prove caching with a faster second run and add a weekly clean-up so disks do not fill. Secret slots are left empty for you to fill, so no credential ever passes through us.

What's included

  • Up to two build machines attached to your existing Git platform
  • Three pipelines passing on your real code, plus one deploy step if you want it
  • Your build and test commands run first, so problems surface on day one
  • Job isolation chosen with you, with any trade-offs written down
  • Caching proven by a faster second run, and weekly clean-up of build disks
  • Named, empty secret slots that you fill: no credentials pass through us
  • A handover listing every job, every secret slot and the disk sizing

How it works

  1. 01

    Book and send access

    Book online with your ABN or NZBN. We tell you exactly what access and material we need; the clock starts once we have it.

  2. 02

    We do the work

    An experienced employee who specialises in this task works through it, and asks before anything outside the scope.

  3. 03

    Delivered with evidence

    You get everything listed on this page, with a written account of what was done.

Before you order

Have these ready so we can start the moment you order. The delivery clock only runs while we have them.

Who it's for

A team whose code is already in GitHub, GitLab, Forgejo or Gitea, with nothing set up to run builds.

Questions

What if our build already fails?

We tell you on day one with the failing command and its output, and finish everything else. Fixing your build or tests is a Developer Day.

How is this different from The Self-Hosted Git Setup?

That task builds the Git server and deliberately runs no builds. This one adds the runners and pipelines. You can buy either, or both.

Can you set up Jenkins?

No. Modern Git platforms include CI already, so we use the one you have rather than add a separate server to maintain.

Often booked alongside