CI/CD with Jenkins & GitHub
Declarative vs Scripted Pipelines
CI/CD with Jenkins & GitHub
0% Completed
Introduction to CI/CD
This topic lays the foundation for the course by explaining what CI/CD is and why it has become essential in modern software development, along with a broad look at the tools used to implement it.
This topic gets students hands-on with Jenkins, the most widely used open-source automation server, covering installation, navigation, and creating a first working job.
This topic covers the GitHub-specific concepts needed to integrate version control with CI/CD pipelines, focusing on how repository events trigger automated workflows.
This topic dives into how Jenkins pipelines are structured and written, moving students from simple manual jobs to fully automated, code-defined pipelines.
This topic covers how automated testing is integrated into Jenkins pipelines, ensuring that code is validated at every stage and that teams are quickly alerted when something breaks.
This topic covers how Jenkins is used to automatically deploy applications after successful builds and tests, along with strategies for managing sensitive data and recovering from failed deployments.
This topic introduces GitHub Actions, GitHub's native CI/CD tool, giving students a comparison point to Jenkins and helping them understand when each tool might be the better choice.
This topic brings together everything learned so far into a hands-on project, giving students practical experience building and running a complete CI/CD pipeline from start to finish.
This final topic helps students understand the certification landscape related to CI/CD and DevOps tools, preparing them for the next steps in advancing their careers in this field.
This lesson covers the two syntax styles for writing Jenkins pipelines — declarative (simpler, structured) and scripted (more flexible, Groovy-based) — helping students choose the right approach for their needs.