BeginnerModernization36 min
Jenkins and CI/CD pipelines
How a change travels from a commit to production without manual copying: CI/CD in plain words, Jenkins controllers, agents and Jenkinsfiles, packaging build outputs into versioned binaries, and deploying them safely.
What you will be able to do
- Explain continuous integration, continuous delivery and continuous deployment, and how they differ
- Describe the parts of Jenkins and read a declarative Jenkinsfile
- Explain how build outputs are packaged, versioned and stored as artifacts
- Describe a safe deployment: promotion through environments, approvals, checks and rollback
Lessons
- CI/CD in plain wordsContinuous integration means every change is merged often and automatically built and tested, so problems show up within minutes.
- Jenkins: controller, agents, jobs and pluginsJenkins is a free, open-source automation server written in Java. The controller holds the configuration, schedules work and shows the results; agents are the machines that…
- Pipelines as code: reading a JenkinsfileA Jenkinsfile describes the pipeline in a file stored with the code. A declarative pipeline names the agent to run on, a list of stages each containing steps, and a post section…
- Packaging binaries: artifacts, versions and repositoriesPackaging turns build outputs into one versioned file, called an artifact, that can be stored, checked and deployed.
- Deploying a package safelyA safe deployment takes the same package through each environment in turn, with configuration supplied separately for each one.
Track your progress and earn a certificate.
Free account, 30 quiz questions for this subject.