CI/CD
Continuous integration and delivery (CI/CD): every change is tested automatically, and changes that pass are ready to ship without manual steps. CivicGrid's pipeline runs on GitHub Actions, and I'm learning Jenkins alongside it, because so many teams still run it.
Learning track · 9 lessons
CI/CD with GitHub Actions and Jenkins
One real pipeline, built in two tools side by side: GitHub Actions, which runs CivicGrid's pipeline, and Jenkins, the server many companies still run themselves. From what CI/CD solves to tests as gates, images, secrets, scanning and the handoff to production.
- 1What CI/CD solvesStart · 20 min
- 2One pipeline, two toolsStart · 35 min
- 3Tests as gatesStart · 45 min
- 4Building and tagging imagesStart · 25 min
- 5Secrets and permissionsStart · 25 min
- 6Pipelines that still work next monthStart · 20 min
- 7Security scanning in the pipelineStart · 25 min
- 8From image to productionStart · 25 min
- 9Running Jenkins yourselfStart · 25 min
Tools to know
GitHub Actions (opens in a new tab)
CI/CD built into GitHub. Workflows are YAML files in your repository.
Jenkins (opens in a new tab)
The long-running CI/CD server many companies still run. Pipelines live in a Jenkinsfile.
Jenkins logo by the Jenkins project, licensed CC BY-SA 3.0.
From www.kwamib.dev/resources/cicd
Git
Linux
Python
SQL
Networking and DNS
Docker
Kubernetes
Terraform
Compliance
Argo CD
Ansible
Monitoring and alerting
Automation
AWS
Security
Local LLMs
Web development
Career and certs