Continuous Integration & Deployment

Pipelines that build, test and deploy every change on their own: required checks, artifacts built once, safe secrets, fast feedback, deploy strategies with automatic rollback, and the routines that keep it all green.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Continuous Integration & Deployment, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

199

Starter tasks

⚙️ Software Engineering

Continuous Integration & Deployment

Setting up pipelines that build, test and deploy every change automatically, keeping them fast, reliable and safe to release from.

  1. Map of every pipeline the team runs today
  2. Choosing a CI platform the team will keep
  3. Build, lint and unit tests on every pull request
  4. Required status checks and branch protection
  5. Pipeline definitions kept in the repository
  6. Reproducible builds with pinned toolchains
  7. Build once, promote the same artifact
  8. Short-lived cloud credentials for pipelines
  9. First automatic deploy to staging
  10. Agreeing what a green main branch means
  11. Broken main branch rota
  12. Weekly pipeline health review
  13. Infrastructure failure triage for CI jobs
  14. Self-hosted runner fleet upkeep
  15. CI secret and deploy token rotation
  16. CI minutes and runner cost budget
  17. Automatic deploy log and change records
  18. Shared pipeline template and action upgrades
  19. Deploy freeze and change window calendar
  20. Quarterly rollback drill
  21. Advanced pipeline syntax on your CI platform
  22. Dependency caching that actually hits
  23. Splitting test jobs across parallel runners
  24. Rolling, blue-green and canary deploys compared
  25. Running the pipeline locally before pushing
  26. Methodical debugging of failing pipeline jobs
  27. Database migrations as a gated pipeline step
  28. Feature flags to separate deploy from release
  29. Cutting pull request feedback to under ten minutes
  30. Adopting a merge queue
  31. Moving to trunk-based development
  32. Preview environments for each pull request
  33. Deciding on continuous deployment to production
  34. Automatic rollback on failed health checks
  35. Hosted versus self-hosted runners
  36. Shared pipeline templates instead of copies
  37. Migrating off an old CI server
  38. First production deploy of a new service
  39. Break-glass deploy when CI is down
  40. Preparing pipelines for a peak trading period
  41. Change management evidence for an audit
  42. CI and deploys for a solo developer
  43. Learning an unfamiliar pipeline in your first weeks
  44. Taking over pipeline ownership from a departing engineer
  45. Safe CI for contributions from forks
  46. Segregation of duties in a regulated pipeline
  47. Signed artifacts and build provenance
  48. Automated canary analysis on live metrics
  49. Pull-based GitOps deployment
  50. Hardening runners against pipeline attacks

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Map of every pipeline the team runs today

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Before changing anything, write down what actually happens between a push and a production deploy: which jobs run, where, how long they take and which steps are still done by hand. Teams are often surprised to find a forgotten cron job deploying from a laptop or a nightly build nobody reads.

First tasks

  • List every repository that has a pipeline file or a build job
  • Export the last thirty runs of the main pipeline with durations
  • Walk a teammate through a deploy and note every manual step
  • Agree the top three pain points at the next team meeting

Choosing a CI platform the team will keep

Teams that pick a CI service because a tutorial used it often find, a year later, that it cannot run their jobs on the hardware they need or that the bill has tripled. Scoring two or three hosted and self-hosted options against your real workloads, security needs and budget gives a choice you can defend and will not revisit every quarter.

First tasks

  • Write the list of must-have and nice-to-have CI requirements
  • Shortlist three CI platforms that meet the must-haves
  • Port one representative pipeline to the top two candidates
  • Record the decision and the twelve-month cost estimate

Build, lint and unit tests on every pull request

If tests only run when someone remembers, broken code reaches the main branch and the next person to pull pays for it. A first pipeline that compiles the code, runs the linter and the unit tests on every pull request is the single change that makes the rest of this area possible. Keep it simple and fast at first, under ten minutes, and add stages later.

First tasks

  • Write the commands that build and test the project from a clean checkout
  • Add a pipeline file that runs those commands on pull requests
  • Make the job report its status back to the pull request
  • Time five runs and trim any step over two minutes

Make it yours.

Install Continuous Integration & Deployment, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.