🔁

CI/CD: Concepts & Tools

35 cards · 🇺🇸 English

Continuous integration and delivery concepts, pipelines, and common tools.

Study all 35 cards for free

Flashcards, quizzes, pixel-art games and a daily review that remembers for you.

Study this deck free

Try the first 10 cards

1 / 10
Question

CI/CD

Knew itLearning

Tap the card for the answer · swipe right if you knew it, left if not

Already have an account? Sign in

Cards

  1. 1CI/CD
    Continuous Integration and Continuous Delivery (or Continuous Deployment)
  2. 2Continuous Integration (CI)
    The practice of integrating source code changes frequently and ensuring the integrated codebase is in a workable state
  3. 3Continuous Delivery (CD)
    Producing software in short cycles with high speed and frequency so that reliable software can be released at any time
  4. 4Continuous Deployment
    Automatic rollout of new software functionality directly into production without manual intervention
  5. 5CI/CD pipeline
    The sequence of continuous integration, continuous delivery, and continuous deployment processes occurring in order
  6. 6Core activities of CI
    Developers co-locate code changes in a shared integration area frequently, and the resulting integrated codebase is verified for correctness
  7. 7How often should developers integrate code changes?
    At least once a day, though more frequently is better - after each commit is ideal
  8. 8'integration hell' or 'merge hell'
    When the repository becomes so different from developers' baselines that the time to integrate exceeds the time it took to make the original changes
  9. 9Build automation
    Automating the process of compiling source code into binaries, running tests, and generating artifacts using build automation tools
  10. 10What should a single command do in a CI system?
    It should have the capability of building the entire system
  11. 11Atomic commit
    A commit where all of a developer's changes are handled as a single unit, required by CI systems
  12. 12Test-driven development in CI context
    Writing tests before code and ensuring all unit tests pass locally before committing to the integration branch
  13. 13Feature toggles
    Mechanisms to disable incomplete features before committing, allowing continuous integration without breaking the build
  14. 14What quality control checks does a CI server typically perform?
    Running unit tests, static analysis, performance testing, and collecting software quality metrics
  15. 15Deployment automation in CI/CD
    Automating the deployment of built software to a production-like environment or directly to production
  16. 16What CI best practice relates to bug fixes?
    Every bug-fix commit should come with a test case that reproduces the bug to prevent regression
  17. 17Why should the build be kept fast?
    So that if there is a problem with integration, it is quickly identified and developers can fix it immediately
  18. 18Staging environment
    A pre-production environment that is a scalable version of production, used for testing before deployment
  19. 19Service virtualization
    Simulating dependencies (APIs, third-party services, mainframes) that are beyond the team's control or too complex to configure in test environments
  20. 20Main benefits of CI
    Earlier bug detection, reduced effort to find bug causes, avoiding integration chaos, frequent availability of working builds, and quick feedback on changes
  21. 21Main risks of CI
    Build system setup effort, maintaining automated tests, value depends on test quality, and high build latency limits effectiveness
  22. 22Regression testing
    Testing to ensure that previously fixed bugs do not reappear when new changes are made
  23. 23What modern DevOps practices involve CI/CD?
    Continuous development, continuous testing, continuous integration, continuous deployment, and continuous monitoring
  24. 24What metrics can CI systems collect?
    Code coverage, code complexity, test results, build times, and other software quality metrics
  25. 25Principle of least privilege in CI/CD
    Granting only the minimum permissions necessary for CI/CD processes while implementing security controls to minimize risk
  26. 26How often should developers update from the repository?
    All programmers should start the day by updating the project from the repository to stay synchronized
  27. 27Build light indicator
    A visual indicator (often a physical device) showing the current build status to the entire team
  28. 28What should the CI system do when a build breaks?
    Make it easy to find out who made the relevant change and what that change was for quick resolution
  29. 29Main branch in version control
    The primary integration branch where all developers merge their changes, ensuring everyone works from a common codebase
  30. 30Lean software development
    A methodology that includes continuous delivery practices, inspired by lean manufacturing principles

And 5 more cards. Study the whole deck free

Articles about this deck

More Programming decks

See all
Study all 35 cards free