Building, packaging and running every check automatically on each change.

On the map: Build & Package CI/CD

1. Package managers and dependencies Beginner 10 min read ✓ Learned

   Install the libraries a project needs, pin their versions with a lock file and keep them up to date.

   Before this: Git basics

2. Build artifacts and versioning Intermediate 10 min read ✓ Learned

   Build once, give the result a version, and deploy that same artifact to every environment.

   Before this: Package managers and dependencies, Automated tests

3. CI/CD pipelines Intermediate 12 min read ✓ Learned

   Run tests, checks and the build automatically on every push, and deliver only what passes.

   Before this: Automated tests, Branches and pull requests

Technologies & Frameworks

Tools you are likely to meet with these topics. They are options, not requirements: you do not need any of them to mark a topic as learned, and nobody uses them all. Pick one when a project calls for it.

With Build artifacts and versioning

• Docker BuildKit

  Tool

  The build engine behind docker build: parallel build steps, build caches and secrets that do not end up in the image.

  Learn first: Containers with Docker

  BuildKit ↗ — Docker BuildKit, official documentation, opens in a new tab Official · Docker

With CI/CD pipelines

• GitHub Actions

  Platform

  CI/CD built into GitHub: workflows in YAML files in the repository run on pushes, pull requests or a schedule.

  Recommended for: Repositories hosted on GitHub

  Learn first: Git basics

  Quickstart for GitHub Actions ↗ — GitHub Actions, official documentation, opens in a new tab Official · GitHub

• GitLab CI/CD

  Platform

  CI/CD built into GitLab: a .gitlab-ci.yml file defines the stages and jobs that run on each change.

  Recommended for: Repositories hosted on GitLab

  Learn first: Git basics

  Create and run your first GitLab CI/CD pipeline ↗ — GitLab CI/CD, official documentation, opens in a new tab Official · GitLab