Skip to main content

A Jenkins plugin a day... Job Config History

Hundreds of plugins are currently available for Jenkins in the official update center, but some of them in particular make my team daily job easier and enjoyable. I will go through some of them in the next months in this blog. Here's the first one: the configuration history plugin (https://wiki.jenkins-ci.org/display/JENKINS/JobConfigHistory+Plugin ), useful but with a very poor Wiki documentation.
This plugin allows to check for changes in both Jenkins system and jobs configurations and allows to revert back to an older release of the same build job/system config. Everything could be managed through the Jenkins Dashboard only. The history repo is created in the same master host. So you need to take in account some space in one of the local disk partitions used by the Jenkins master and periodically check for history that you don't need any more and that could be discarded. Any way the plugin provides several configuration settings in the Jenkins global configuration (Manage Jenkins -> Configure System) to set up and tune the disk space as well:



This plugin requires the Jenkins release 1.554.1 or later in order to work properly. It installs successfully in the prior releases, but some features don't work. It has no dependencies from other plugins.
Once installed the plugin adds an extension point to the Dashboard:



From there you can see the overall configuration change history for the Jenkins instance and filter it by scope:



The following is the same view above filtered to show the build jobs configuration history only:



Clicking on a job configuration name you can see the full list of changes for the given job:


Through this view you can revert to any of the older configurations. To revert back to a different configuration you don't need to restart the Jenkins server.


It is possible also to restore a deleted build job through the Restore Project button:


No need to restart the server to restore a deleted project.
The links in the Show File column for each view show the selected configuration in the web browser in XML mode:




or plain text:



It is possible to quickly access the change history of a single build job simply moving to its project page and clicking on the Job Config History link on the left:


Comments

Popular posts from this blog

Turning Python Scripts into Working Web Apps Quickly with Streamlit

 I just realized that I am using Streamlit since almost one year now, posted about in Twitter or LinkedIn several times, but never wrote a blog post about it before. Communication in Data Science and Machine Learning is the key. Being able to showcase work in progress and share results with the business makes the difference. Verbal and non-verbal communication skills are important. Having some tool that could support you in this kind of conversation with a mixed audience that couldn't have a technical background or would like to hear in terms of results and business value would be of great help. I found that Streamlit fits well this scenario. Streamlit is an Open Source (Apache License 2.0) Python framework that turns data or ML scripts into shareable web apps in minutes (no kidding). Python only: no front‑end experience required. To start with Streamlit, just install it through pip (it is available in Anaconda too): pip install streamlit and you are ready to execute the working de...

Load testing MongoDB using JMeter

Apache JMeter ( http://jmeter.apache.org/ ) added support for MongoDB since its 2.10 release. In this post I am referring to the latest JMeter release (2.13). A preliminary JMeter setup is needed before starting your first test plan for MongoDB. It uses Groovy as scripting reference language, so Groovy needs to be set up for our favorite load testing tool. Follow these steps to complete the set up: Download Groovy from the official website ( http://www.groovy-lang.org/download.html ). In this post I am referring to the Groovy release 2.4.4, but using later versions is fine. Copy the groovy-all-2.4.4.jar to the $JMETER_HOME/lib folder. Restart JMeter if it was running while adding the Groovy JAR file. Now you can start creating a test plan for MongoDB load testing. From the UI select the MongoDB template ( File -> Templates... ). The new test plan has a MongoDB Source Config element. Here you have to setup the connection details for the database to be tested: The Threa...

Evaluating Pinpoint APM (Part 1)

I started a journey evaluating Open Source alternatives to commercial New Relic and AppDynamics tools to check if some is really ready to be used in a production environment. One cross-platform Application Performance Management (APM) tool that particularly caught my attention is Pinpoint . The current release supports mostly Java applications and JEE application servers and provides support also for the most popular OS and commercial relational databases. APIs are available to implement new plugins to support specific systems. Pinpoint has been modeled after Google Dapper and promises to install agents without changing a single line of code and mininal impact (about 3% increase in resource usage) on applications performance. Pinpoint is licensed under the Apache License, Version 2.0 . Architecture Pinpoint has three main components:  - The collector: it receives monitoring data from the profiled applications. It stores those information in HBase .  - The web UI: the f...