How teams build, test, release and run software with automation: CI pipelines, deployment strategies, Terraform and Ansible, artifact versioning, pipeline secrets and GitOps.
You’re reading a free preview. Sign up to see every topic and question — and to play this deck as games.
How CI pipelines build and test every change: stages, runners, caching, artifacts, flaky tests and reproducible builds, using GitHub Actions and GitLab CI terms.
40 total questions
Card #1
What is continuous integration (CI)?
Card #2
What is a CI/CD pipeline?
Card #3
What is a runner (or agent) in CI?
1. One test breaks about one pipeline run in twenty with no code edits, and people now just press re-run until it goes green. What should the team do?
2. A pipeline's dependency cache is keyed only on the branch name. After someone updates the lockfile, builds keep using old library versions. What is the fix?
3. The test stage compiles the app from source again instead of using the binary the build stage produced, and the deploy stage compiles it a third time. What is the main risk?
1. A ___ is a tool that checks code for style problems and likely bugs without running it.
Hint: A static analysis tool, ESLint is one
2. In GitHub Actions, the ___ key picks the kind of machine a job runs on, such as ubuntu-latest.
Hint: Two words joined by a hyphen
3. Build tools such as Gradle and Bazel skip steps whose inputs have not changed, which is called an ___ build.
Hint: Only the changed parts are rebuilt
