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

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

jOOQ: code generation in Eclipse

jOOQ allows code generation from a database schema through ANT tasks, Maven and shell command tools. But if you're working with Eclipse it's easier to create a new Run Configuration to perform this operation. First of all you have to write the usual XML configuration file for the code generation starting from the database: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <configuration xmlns="http://www.jooq.org/xsd/jooq-codegen-2.0.4.xsd">   <jdbc>     <driver>oracle.jdbc.driver.OracleDriver</driver>     <url>jdbc:oracle:thin:@dbhost:1700:DBSID</url>     <user>DB_FTRS</user>     <password>password</password>   </jdbc>   <generator>     <name>org.jooq.util.DefaultGenerator</name>     <database>       <name>org.jooq.util.oracle.OracleDatabase</name>     ...

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...