Tutorial : Renaming a Jenkins build

CD/CI is an inseparable part of our automation and build verification. None of our test executions are done locally now but only through CDCI tools like Jenkins.

Through this tutorial I am trying to solve a day to day problem while executing Jenkins jobs. What was the problem we faced and how did we resolve it.

Problem : One of the major problems that we were facing in our project while executing Jenkins jobs was understanding which builds were executed when. With large number of team members executing Jenkins pipelines , it was becoming a challenge to recognize and find the right execution done by the respective team member. Or as a matter of fact , which test suite has been run.

Reason : The main reason for this challenge and confusion was that the build names were very generic. The build names were not giving any information on which pipelines and the jobs were being run. Who had triggered those jobs etc. This led to the triggered jobs having a default format of the build names.

Default build name for our project:

As you can see above, the build name does not let you know which pipeline is being executed , who has triggered. Infact, there are static values which are of no use for the user to understand which build has got executed. Therefore, we had to come up with the new build…