Heard of JCasC and Not Sure Where to Start? Let me Help You!
summary
Shows how Jenkins Configuration as Code (JCasC) actually runs: Docker-built Jenkins images (repo jcasc-core) and a separate repo for YAML configs (jcasc-conf), images built by GitHub Actions and versioned with short SHAs, plugins installed via install-plugins.sh from a plugins.txt with pinned versions, and Jenkins started with environment variable CASC_JENKINS_CONFIG pointing to the YAML. Startup takes ~20–30 seconds, you can reload configs without losing state, and keeping a copy of JENKINS_HOME lets roll back safely.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 0:44Jenkins journey and challenges
- 5:40Birth of JCasC plugin
- 6:22How JCasC works
- 8:12Official resources and demos
- 9:56Docker image setup
- 13:51Agent configuration
- 14:55GitHub Actions workflow
- 15:38Docker Compose setup
- 17:46Starting Jenkins with JCasC
- 19:56Verifying Jenkins startup
- 20:38Tips for configuration files
- 23:11Avoiding documentation use
- 24:55Credentials configuration
- 26:22Protecting Jenkins home
related talks
50m"Look Ma, No Hands" - Jenkins Configuration-as-Code
33mJenkins 101
51mJenkins Configuration as Code - Automate your automation Server
35mJenkins Scaling and Organization for an Efficient CI
51mJenkins or: How I learned to stop worrying and love automation
42mZero to Jenkins: Automatic builds + deploys
06mJenkins X: Lessons Learned
36mUsing Jenkins to Build, Deploy, and Automate Projects