Jenkins Pipelines allows you to treat all of your build logic as code. You can also integrate your build into a larger automated process that includes things like automated deployment. Pipelines are especially useful as you transition from doing CI to doing CI+CD. In this exercise, you will build a simple pipeline for a sample application. You will gain a basic familiarity with how a Jenkins Pipeline is created and how to implement simple build logic within a pipeline.
Successfully complete this lab by achieving the following learning objectives:
- Create a new Multibranch Pipeline project in Jenkins called train-schedule.
In Jenkins, click on New Item. For the item name, type train-schedule, and select Multibranch Pipeline.
Then click the OK button.
- Successfully build the master branch of the train-schedule pipeline project.
Fork this project in GitHub: https://github.com/linuxacademy/cicd-pipeline-train-schedule-pipelines
On the master branch, create a Jenkinsfile. In the Jenkinsfile, create a stage that executes the gradle build with
./gradlew build --no-daemonand archives the dist/trainSchedule.zip artifact.
Configure the train-schedule multibranch pipeline project in Jenkins to build the source code from your GitHub fork and execute the build on the master branch successfully. This should produce the dist/trainSchedule.zip archived artifact.