DevOps Continuous Integration Flashcards

24 sample cards from the Continuous Integration deck

Sampled from the end of the deck, so these are different cards from the ones shown on the syllabus page.

1. In CircleCI, what is an 'executor'?

   The underlying environment in which a job's steps run - for example a Docker image, a Linux/Windows VM (machine), or a macOS environment.

2. What is GitLab CI/CD?

   The built-in continuous integration and delivery system of GitLab, configured via a '.gitlab-ci.yml' file and executed by GitLab Runners.

3. What configuration file does GitLab CI/CD use?

   A YAML file named '.gitlab-ci.yml' in the root of the repository.

4. What is a 'GitLab Runner'?

   An agent application that connects to GitLab and executes the jobs defined in '.gitlab-ci.yml'; runners can be shared, group-specific, or project-specific and run jobs using executors like Docker or shell.

5. In GitLab CI/CD, what is a 'stage' and how do stages relate to jobs?

   A stage is a phase of the pipeline (e.g. build, test, deploy). Jobs in the same stage run in parallel; stages run sequentially, and a later stage starts only if the previous stage succeeds.

6. In a GitLab '.gitlab-ci.yml', what does the 'script' keyword in a job define?

   The shell commands the runner executes for that job (the actual work, such as compiling code or running tests).

7. In GitLab CI/CD, what is a 'pipeline'?

   The top-level component composed of stages and jobs that runs automatically (typically on each push/merge request) to build, test, and deploy the code.

8. What data format is most commonly used for CI configuration files across tools like Travis, CircleCI, and GitLab?

   YAML (YAML Ain't Markup Language), a human-readable, indentation-based data serialization format.

9. In YAML CI configs, why is indentation significant?

   YAML uses indentation (spaces, not tabs) to denote structure and nesting; incorrect indentation changes meaning or causes parse errors.

10. What is the difference between defining the pipeline 'as code' versus configuring it through a UI?

    'Pipeline as code' stores the build configuration in a version-controlled file in the repo (reproducible, reviewable, diffable), whereas UI configuration lives in the CI server and is harder to track and reproduce.

11. What are 'environment variables' used for in CI configuration?

    To pass configuration and secrets (API keys, credentials, build flags) into jobs without hardcoding them in the repository; secret variables are typically masked and stored in the CI platform's settings.

12. What is 'caching' in a CI configuration, and why is it used?

    Caching stores dependencies or build outputs (e.g. downloaded packages) between runs so they need not be re-fetched/rebuilt each time, speeding up pipelines.

13. What are CI 'artifacts'?

    Files produced by a job (e.g. compiled binaries, test reports, coverage files) that are saved and can be passed to later stages or downloaded after the pipeline runs.

14. What is automated testing in the CI context?

    The practice of running tests automatically (without manual intervention) on every code change to verify correctness and catch regressions before integration.

15. Define unit, integration, and end-to-end (E2E) tests and order them by scope.

    Unit tests verify a single component in isolation (smallest scope); integration tests verify multiple components working together; end-to-end tests verify the whole system from the user's perspective (largest scope).

16. What is the 'test pyramid'?

    A model recommending many fast, cheap unit tests at the base, fewer integration tests in the middle, and a small number of slow, expensive end-to-end tests at the top.

17. What is 'code coverage' and how is it calculated?

    A metric for the proportion of code exercised by tests. A common form is line coverage: $$\text{coverage} = \frac{\text{lines executed by tests}}{\text{total executable lines}} \times 100\%$$

18. What does a 'self-testing build' mean in CI?

    A build that automatically includes a suite of automated tests, so that a passing build also means the code passed its tests - making the build a reliable indicator of correctness.

19. What is a 'regression test'?

    A test that re-checks previously working functionality to ensure new changes have not broken (regressed) existing behavior.

20. Why are fast tests important in a CI pipeline?

    Because CI runs tests on every commit; slow tests delay feedback and discourage frequent integration, so keeping the build (and test suite) fast preserves the tight feedback loop.

21. What is build automation?

    The practice of scripting and automating the steps to compile source code, resolve dependencies, run tests, and package artifacts, so builds are repeatable and require no manual steps.

22. Name three common build automation tools and the ecosystems they belong to.

    Maven and Gradle (Java/JVM), Make (C/C++ and general), npm/Webpack (JavaScript), and MSBuild (.NET). Each automates compiling, dependency resolution, and packaging.

23. What is a 'reproducible build'?

    A build that produces the same output artifact every time it runs from the same source and configuration, regardless of who runs it or where - achieved by pinning dependencies and isolating the environment.

24. Why are Docker containers commonly used in CI build automation?

    They provide isolated, reproducible, ephemeral environments with pinned dependencies, ensuring builds and tests run identically on any machine and avoiding the "works on my machine" problem.

What this deck covers

Continuous Integration flashcards FAQ