Cloud Computing · DevOps

DevOps and CI/CD Terms

Continuous integration, continuous deployment, and DevOps pipeline concepts.

39 cards · basic cards · AI-written, checked twice. Edit anything.

Study this set free Get FlashKeepers for iPhone
What does CI stand for in DevOps?
Continuous Integration
What does CD stand for in DevOps?
Continuous Deployment or Continuous Delivery
What is a build pipeline?
An automated sequence of stages that compiles code, runs tests, and prepares software for release
What is the purpose of a linter in the CI/CD pipeline?
To check code for style violations and potential bugs before deployment
What is artifact storage in DevOps?
A repository that stores compiled binaries, packages, or build outputs for deployment
What is blue-green deployment?
A deployment strategy where two identical production environments (blue and green) are maintained, with traffic switched between them for zero-downtime releases
What is a webhook in CI/CD?
An automated callback that triggers a pipeline when an event occurs, such as a code push
What does YAML stand for?
YAML Ain't Markup Language
What is containerization?
Packaging an application and its dependencies into a lightweight, isolated, executable unit
What is an infrastructure-as-code (IaC) tool?
Software that manages and provisions infrastructure (servers, networks, storage) through code and configuration files instead of manual processes
What is the purpose of environment variables in CI/CD?
To store sensitive data (API keys, passwords, credentials) and configuration values that differ between environments without hardcoding them
What is a release candidate (RC)?
A build that is ready to be promoted to production pending final testing and approval
What is rollback in DevOps?
The process of reverting a deployment to the previous stable version if issues are detected
What does immutable infrastructure mean?
Infrastructure that is never modified after deployment, instead being replaced entirely with a new version
What is canary deployment?
A deployment strategy where new code is rolled out to a small subset of users or servers first to test for issues before full rollout

24 more cards in the app