CoreQ Academy5.2 Explain concepts related to continuous integration/continuous deployment (CI/CD) pipelines.
A CI/CD pipeline turns code into running software automatically. It is also a high-value target: protect its credentials and verify what it builds.
Pipeline stages
- Automation
- Every step runs without manual work, making releases repeatable.
- Code integration
- Merging and building changes frequently so problems surface early.
- Code deployment
- Automatically releasing built artifacts to environments.
- Build
- Compiling and packaging code into artifacts.
- Testing
- Unit, integration and regression tests run on every change.
- Security
- SAST, dependency scanning, secret scanning, image scanning and policy checks in the pipeline.
- Workflow
- The defined sequence of jobs and approvals.
- Artifacts
- The outputs of a build, stored, versioned and ideally signed.
Artifact types
- Images
- Deployable machine or container images.
- VM
- Golden virtual machine images.
- Container
- Container images pushed to a registry.
- Packages
- Installable software bundles.
- Red Hat Package Manager (RPM)
- Package format for RHEL, Fedora and related distributions.
- Debian
- .deb package format for Debian and Ubuntu.
- ZIP
- Compressed archive format, common for functions and web bundles.
- tar
- Unix archive format, often compressed (.tar.gz).
- Flat file
- A single uncompressed file artifact, such as a script or binary.
Repositories
- Public
- Anyone can read; never put secrets or internal code there.
- Private
- Restricted access for internal code and artifacts.
Check your understanding
Loading quiz…
Original CoreQ Academy material, mapped to objective 5.2 of the publicly available CompTIA Cloud+ CV0-004 exam objectives (Exam objectives V4, document version 5.0). Not affiliated with or endorsed by CompTIA. Contains no exam questions.