Following on from the second post in the series, this article will describe basic steps for configuring the first pass at our Jenkins pipeline.
1) frontend Build job creation
If you have followed the second post, Jenkins should now be up and running and accessible by going to http://192.168.99.100:8080 (or whatever IP your Docker host is running on).
You should see a screen that resembles figure 1 below.
Click on ‘New Item‘, a new screen will load.
Enter ‘spring-boot-frontend‘ for the ‘Item name‘
Ensure ‘Maven project‘ is selected
On the resulting screen under ‘Source code management‘, choose ‘Git‘
Enter ‘https://github.com/eggsy84/spring-boot-frontend.git‘ in to the ‘Repository URL‘ field. (You can of course change this to your SCM location)
Scroll down to the ‘Build triggers‘ section
Choose ‘Poll SCM‘ and enter ‘* * * * *‘ in to the schedule field (This means poll every minute)
Scroll down to the ‘Build‘ section
Enter ‘clean compile -DskipTests=true‘ in to the ‘Goals and options‘ field
Scroll down and click ‘Save‘
After clicking Save you will be returned to the job dashboard. A build job should automatically trigger as shown in figure 2.
That job will take a number of minutes to complete whilst it downloads the various Maven dependencies. You can click in to the job and choose ‘Console’ to monitor the progress.
Once complete the console should look similar to figure 3 below.
Congratulations, you just created your first Maven based Jenkins job!