In this series of liveProjects, you’ll use pipeline-as-code techniques and Jenkins infrastructure to set up new CI/CD pipelines for software development. Stepping into the role of an automation engineer looking for a better way to manage application lifecycle activities, you’ll implement DevOps practices such as continuous integration and continuous delivery using Jenkins Pipeline (pipeline-as-code). To do this, you’ll use a declarative pipeline and Blue Ocean to create a Jenkinsfile for pipeline-as-code adoption. CI/CD pipelines that are iterated as pipeline-as-code are some of the most robust and easy-to-use features of Jenkins for non-technical colleagues.
For any beginners these projects will be a good start with Jenkins pipeline.
In this liveProject, you’ll overhaul the CI/CD pipeline of a news and entertainment company to make it fit-for-purpose for an Agile cultural transformation. In order to create a pipeline that can manage quality, execute tests, calculate code coverage, and efficiently deploy applications or microservices, you’ve decided to implement pipeline-as-code. You’ll use Jenkins for the setup, then automate tasks and ensure they’re reliable, efficient, and repeatable. Your challenges include installing Jenkins, executing your pipeline to automation requirements, distributing architecture to manage the load on Jenkins, and quickly executing modifications to your pipeline.
In this liveProject, you’ll use Jenkinsfile to store pipeline script in a version control system. You’ll first create a declarative pipeline using Jenkinsfile, then generate a pipeline script using pipeline syntax. These challenges will help build your understanding of the basics of pipeline creation in declarative syntax.
In this liveProject, you’ll create a CI/CD pipeline using pipeline-as-code and Blue Ocean. Blue Ocean is a new user interface that allows beginners and non-technical users to graphically create, visualize, and diagnose CI/CD pipelines. Your company needs all employees to be able to work with this pipeline irrespective of their technical backgrounds, so you’ll ensure that this pipeline is easy to replicate without scripting experience. You’ll ensure that specific steps can be executed after a pipeline or stage is complete.
In this liveProject, you’ll create and configure a multi-branch pipeline, then group it in one pipeline-as-code project with Jenkins so all the pipelines for a repository are managed together. Working for a mature company with a well-established but branching CI/CD pipeline, you’ll manage pipelines in different branches available in the repository. The multi-branch pipeline helps maintain pipelines easily when there are many repositories and each has different branches that need to be managed.
This liveProject is for beginner to intermediate automation engineers. To begin this liveProject you will need to be familiar with the following:
Note: These projects use Amazon EC2 instances, which require a paid AWS account.
In this liveProject, you’ll learn basic use cases and best practices for implementing CI/CD pipeline-as-code with Jenkins.