Up to now, we have covered all specific tasks that are individual and can work as a stepping stone to performing other steps, such as static code analysis, Continuous Integration, Continuous Delivery, and Continuous Testing.
What if we need to fix the sequence of execution of all such tasks with or without manual intervention?
What if we want to create a pipeline where one successful execution of Job can lead to another execution of Job?
This is where we will utilize the Build Pipeline plugin and the Pipeline as a Code feature available in Jenkins 2 for the orchestration of the end-to-end automation of Application Life Cycle Management. We have executed a pipeline and all build jobs on a Windows system. Based on your operating system, there might be some changes that you may need to do and we have mentioned these as comments at specific places in the script or code.
This chapter will cover how to orchestrate a build job to execute it in a specific...