Automate Jenkins with Groovy
In this lab, you'll explore three challenges from the associated course: using the script console to reset a build number, creating a Hello World groovy pipeline script, and configuring your Jenkins instance with a startup script.
Terms and conditions apply.
Challenge
Get Started in the Lab Environment
Here are the initial instructions and explanation of the lab environment. Read this while your environment is busy creating itself from nothing. Yes, this violates physics; we know. How fun!
Challenge
Working in the Script Console
You’ve got a failed build for a software library that triggers a process in another system. The build problem has been corrected so that the next build will succeed, but having a gap in the build numbers will create headaches in the target system. You want to delete the failed build, and reset the build counter. Then, the next successful build will have the build number of the current failed build.
Challenge
Create a Pipeline Build
As an admin, you’re concerned that the builds are not in version control, so you want to migrate from Freestyle builds to Pipeline builds. As a first step, you will create a simple Hello World pipeline build using Groovy as an inline script.
Challenge
Configure Jenkins with a Startup Script
Your security officer has initiated a new policy requiring fresh logins for tools, specifically to disallow the Remember Me box on Jenkins. You’ll create a startup script that will make the Remember Me box on the Jenkins login screen disappear.
Provided environment for hands-on practice
We will provide the credentials and environment necessary for you to practice right within your browser.
Guided walkthrough
Follow along with the author’s guided walkthrough and build something new in your provided environment!
Did you know?
On average, you retain 75% more of your learning if you get time for practice.
Recommended prerequisites
- Basic Jenkins competence
- Knowledge of some scripting language