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.
Your git platform already has continuous integration inside it. It has no machine to run the jobs, which is why a workflow file can sit there queued while nothing happens.
We build up to two machines, attach them to the platform you already run, and deliver three pipelines that run the commands your project runs today. Each one is handed over green on your real code, with its build time recorded and its cache proven on a second, faster run.
Before we write a single pipeline we run your build and test commands on the machine and show you what came back. A build that fails today will fail here too; we tell you which command, and your fixed price stays fixed.
What's included
Up to two build machines attached to the platform you already run, each running as many jobs at once as its cores and memory allow
Three pipelines running the commands your project runs today, handed over green on your real code — plus one deploy step to a server or registry you own, where you want one
Your build and test commands run on the machine before a single pipeline is written, so you find out on day one whether the build works rather than at handover
A choice of isolation described honestly: every job in its own container, or straight on the machine with the trade-off written down and signed
Caching proven by a second run that finishes faster, and a weekly clear-out so the build machine does not fill its disk
Named, empty secret slots you fill in yourself — no registry password, deploy credential or signing key passes through us at any point
A handover naming every pipeline job, every secret, the arithmetic behind the disk numbers, and what nobody here is doing for you afterwards
Before you order
Have these ready so we can start the moment you order. The delivery clock only runs while we have them.
The address of your Forgejo, Gitea or GitLab, a runner registration token, and read access to the repositories we build
One or two Linux build machines with sudo access over SSH
For each repository (up to three): its address, its stack, and the exact commands you run today to install, build and test it
Your isolation choice: a container image every job runs in, or the toolchains installed on the machine itself
Rough sizes: your largest checkout plus build, your largest build output, builds per day, and how long to keep outputs
Where failed-build alerts should go, and the person who will merge the pipeline pull request
How it works
Book it — pay the fixed price and tell us the target environment. No scoping call first.
We deliver — an experienced specialist runs our standard workflow for this exact task. You can watch progress and message them in the portal.
Hand-off — you get the deliverables, the documentation, a rollback snapshot, and a walkthrough if you want one.
Who does it
A salaried Support Resort specialist with more than ten years in the field, working from a runbook we've been refining since 2003 — supervised by senior management, never a marketplace contractor. You'll see who is assigned and can message them about this task directly in your portal.
FAQ
Ask about this task
Our assistant knows the scope document and runbook behind this service. Ask what's covered, what isn't, or whether it's the right task for your situation.
Answers come from our published scope documents. Prefer a person? Switch to the "Email us" tab — a senior manager replies personally, usually the same weekday.
Related services
The Self-Hosted Git Setup
Your own git server on your own machine — Forgejo, Gitea or GitLab CE — with every repository you move across proved intact by matching commit IDs on the old host and the new one.
The Server Admin Day
A senior system administrator works a full day on your server backlog, from the patch level nobody has checked to the backup nobody has restore-tested. Book one day or a run of dates, and each day ends with a written account of every hour.
The Observability Stack
Prometheus, Grafana and Loki watching up to 10 of your Linux servers, with eight dashboards proven on your own data and alerts that tell you a disk is filling days before it fills.