Implementing Pipeline as Code Using JenkinsNew
As organizations strive 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 which slows the delivery process. Join Glenn as he describes how pipeline as code gives teams the ability to define and manage an entire DevOps CI/CD pipeline in code, allows them to store pipeline configurations in source control, version them, and independently test them. Glenn discusses how different versions of an application can have different build steps and still function together using multibranch pipelines and presents the benefits of implementing a pipeline with different build steps rather than using the original Jenkins UI based configuration. Leave this tutorial with an understanding of how pipeline as code allows new visualizations to easily pinpoint pipeline failures. Learn how Jenkins implements these new capabilities using the groovy programming language in a predefined file called Jenkinsfile - a configuration file that allows teams to define each step in their pipeline. Understand how using Jenkinsfile benefits developers as they no longer have to manually create Jenkins jobs or actively manage the pipeline and can focus on developing and testing their applications.