Implementing Pipeline as Code Using Jenkins

 

As organizations look to improve the speed with which they deliver software, they increasingly turn to Continuous Integration/Continuous Delivery (CI/CD) pipelines and infrastructure-as-code software architecture and delivery techniques to help leverage value from their DevOps adoptions. While many of the steps in a pipeline are automated, management of the pipeline itself remains a largely manual process. Pipeline as code gives teams the ability to define and manage an entire DevOps CI/CD pipeline in code, allowing them to store pipeline configurations in source control, version them, and independently test them.

 

The Jenkins CI server supports pipeline as code through a concept known as a Jenkinsfile. This is a configuration file that allows teams to define each step in their pipeline. This means that by using a Jenkinsfile, developers no longer have to manually create Jenkins jobs or actively manage the pipeline and can focus on developing and testing their applications.

 

This course is an extension to our Foundations of DevOps—ICAgile Certification course and will teach you practical techniques for building and working with Jenkinsfile. Upon completion of this course, students will understand and have hands-on experience with Jenkinsfile.