We have seen the built-in pipeline concept of Jenkins 2. It is a very flexible and powerful concept, but for that, we need to write a Groovy script. Another way that has an easy learning curve is to use the Build Pipeline plugin. It provides simple visualization of upstream and downstream build jobs. It also enables manual triggers for a situation where we need approval for executing a specific build. We can create a chain of jobs for end-to-end automation. Here, I'm assuming that you are aware of the concept of upstream and downstream build jobs.
To create a build pipeline, follow these steps:
Install the Build Pipeline plugin.
On the Jenkins dashboard, click on the plus sign, which will open a page to create a Build Pipeline View. Provide a View name for the build pipeline, and click on OK:
It is important to configure upstream and downstream build jobs:
We have created multiple build jobs to compile the source code, verify the source code using Sonar, and...