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

Streamsets Data Collector log shipping and analysis using ElasticSearch, Kibana and... the Streamsets Data Collector

One common use case scenario for the Streamsets Data Collector (SDC) is the log shipping to some system, like ElasticSearch, for real-time analysis. To build a pipeline for this particular purpose in SDC is really simple and fast and doesn't require coding at all. For this quick tutorial I will use the SDC logs as example. The log data will be shipped to Elasticsearch and then visualized through a Kibana dashboard. Basic knowledge of SDC, Elasticsearch and Kibana is required for a better understanding of this post. These are the releases I am referring to for each system involved in this tutorial: JDK 8 Streamsets Data Collector 1.4.0 ElasticSearch 2.3.3 Kibana 4.5.1 Elasticsearch and Kibana installation You should have your Elasticsearch cluster installed and configured and a Kibana instance pointing to that cluster in order to go on with this tutorial. Please refer to the official documentation for these two products in order to complete their installation (if you do

Exporting InfluxDB data to a CVS file

Sometimes you would need to export a sample of the data from an InfluxDB table to a CSV file (for example to allow a data scientist to do some offline analysis using a tool like Jupyter, Zeppelin or Spark Notebook). It is possible to perform this operation through the influx command line client. This is the general syntax: sudo /usr/bin/influx -database '<database_name>' -host '<hostname>' -username '<username>'  -password '<password>' -execute 'select_statement' -format '<format>' > <file_path>/<file_name>.csv where the format could be csv , json or column . Example: sudo /usr/bin/influx -database 'telegraf' -host 'localhost' -username 'admin'  -password '123456789' -execute 'select * from mem' -format 'csv' > /home/googlielmo/influxdb-export/mem-export.csv

Using Rapids cuDF in a Colab notebook

During last Spark+AI Summit Europe 2019 I had a chance to attend a talk from Miguel Martinez  who was presenting Rapids , the new Open Source framework from NVIDIA for GPU accelerated end-to-end Data Science and Analytics. Fig. 1 - Overview of the Rapids eco-system Rapids is a suite of Open Source libraries: cuDF cuML cuGraph cuXFilter I enjoied the presentation and liked the idea of this initiative, so I wanted to start playing with the Rapids libraries in Python on Colab , starting from cuDF, but the first attempt came with an issue that I eventually solved. So in this post I am going to share how I fixed it, with the hope it would be useful to someone else running into the same blocker. I am assuming here you are already familiar with Google Colab. I am using Python 3.x as Python 2 isn't supported by Rapids. Once you have created a new notebook in Colab, you need to check if the runtime for it is set to use Python 3 and uses a GPU as hardware accelerator. You