CI/CD Pipeline Setup

Deploying your application is currently a sequence of steps that lived in somebody’s head, and that somebody has gone. This replaces it with a pipeline: a push runs the tests, a passing build deploys, and a bad deploy has a way back. One repository, set up and written down so your own people can use it without calling us.

What you get

• A build, test and deploy pipeline for one repository, on your existing CI provider or one we agree with you
• Environment secrets moved out of the repository and into managed storage
• A rollback path, proven by actually rolling back once before handover
• Documentation of the pipeline committed to your repository, so the next person does not have to reverse-engineer it
• A handover session with whoever will be running it

What this does not cover

• Writing the tests the pipeline runs. A pipeline runs the suite you already have; if there is not one, it can only prove the application builds, and we will say so rather than hand you a green light that means nothing.
• A second repository. The pattern transfers, but each repository is its own setup.
• Repairing an application that cannot be deployed cleanly in the first place. If we find that during setup we stop, tell you what it would take, and let you decide — rather than spending a fixed price on an open-ended problem.
• Your CI provider’s bill and the cost of the environments the pipeline deploys to.
• Pipeline work after handover. Continuing changes are the DevOps Automation Retainer.

Who it fits

An application deployed often enough that doing it by hand has become the risk. If you ship only a few times a year, a $70 Managed Deployment Window each time is cheaper than this and leaves you no pipeline to maintain.