Using Jenkins to Build, Deploy, and Automate Projects
summary
Covers using Jenkins to implement CI/CD by linking GitHub via GitHub webhooks and a Jenkinsfile (declarative or scripted), running branch-specific pipelines that execute parallel docker containers for npm install/build and then deploy to cloud; shows how console output pinpoints failing steps, how checks block merging until green, how to store GitHub personal access tokens, and how Slack/email plugins notify results — a practical, working multi-branch/mono-repo setup that demonstrably builds, tests, and gates deployments.
AI-written summary · about
chapters (17)
- 0:00Intro
- 1:37Automation
- 2:29Why Jenkins
- 3:59CICD
- 8:04Installing
- 9:50Initial Admin Password
- 10:58Project Images
- 11:20Open Blue Ocean
- 13:29Multibranch Pipeline
- 14:03Project Configuration
- 16:28Linking GitHub
- 17:50Default settings
- 20:38scripted pipeline
- 26:38Git checks
- 27:53Notifications
- 29:16Plugins
- 30:10Final Thoughts
related talks
42mZero to Jenkins: Automatic builds + deploys
39mRemove your Testing Bottleneck with CI/CD Pipelines
48mUsing Jenkins Optimally in Feature-Branch Development
27mAutomation, Innovation and Continuous Delivery
51mJenkins or: How I learned to stop worrying and love automation
30mImplementing Continuous Deployment with Jenkins & Gerritt
33mSimplified Continuous Integration with Laravel and Jenkins
04mContinuous Delivery with Jenkins' New Declarative Pipeline & Artifactory