Jenkins Toolset utilizes Jenkins’ REST APIs. The communication is through only HTTP or HTTPS. It supports both.
For the authentication, it uses token. We’ll go over how to do it below.
And you can make changes to the downloaded XML config files directly and the application keeps track on the changes.
When you start Jenkins Toolset, you have to enter the root URL for the target Jenkins instance.
When you hit enter there, you get a following error message at the bottom of the screen.
Jenkins Toolset doesn’t know who you are, so enter your username to the Jenkins instance.
Once you enter your username, you can click on Get Token button to get to the screen where you can generate your token to access the instance of the Jenkins via Jenkins Toolset.
Copy the token and paste it to the textbox on Jenkins Toolset. Once you have your username and token, you can now start to get the data from the Jenkins instance.
You can directly edit jobs in the XML form using Notepad++ or any text editor you would like. If you right click on a job or multiple jobs, you can open them in XML format.
Once, you make changes to the XML file, the changed jobs are marked in red meaning the change is still local and it’s ready to be uploaded.
You can right click the job in red and select Jenkins Server –> Push Job Changes to apply the change to the server side.
When you click Push Job Changes menu item, you get prompted if you are sure to push the change to the server side.
When the job push is successful, you will see a message and the red job turns back to the normal color.
And then, you can open the job with the browser and you can see the changes applied. This feature is very effective if you have hundreds of jobs and you want to mass update something and you wanna do it by doing find and replace operation. Notepad++ can do regex find and replace for each opened file.
To be continued…