Skip to main content

Jenkins User Conference 2014 report

2014 is going to finish in few days. I can say with certainty that the best event I attended this year was the Jenkins User Conference in Berlin (June 25th).


 The Jenkins User Conference 2014 logo

The guys from CloudBees (https://www.cloudbees.com/) did an excellent job in terms of organization and I think they reached the perfection. The location was easy to reach from any place in Berlin and perfect to host an event like this. The halls hosting the 2 talk sessions had big screens, good audio and enough sitting space for all the participants. The food quality was high and the atmosphere was very relaxed and informal, helping people to easily socialize and share ideas. And of course the level of the talks was excellent.
At this event I met for the first time in person Kohsuke Kawaguchi. I already knew that he is a genius, but it was a pleasure to discover that he is also a really wonderful person. 


Meeting Kohsuke during the conference

Here's a quick summary of the most interesting talks I attended during this conference.
Creating High Quality Jenkins Plugins by Christian Langmaan and Robert Hastlowsky (Codecentric). These 2 guys from Codecentric made a talk in the form of a dialogue between them speaking about the meaning of quality in terms of Jenkins plugins development and showing some nice examples of plugins developed at Codecentric. They showed also the solution they implemented in order to safely update plugins on Jenkins servers in different environments (dev, test, stage, production, etc.).



Configuration as Code: The Job DSL Plugin by Daniel Spilker (CoreMedia AG). Daniel is the maintainer of the Job DSL plugin project (https://wiki.jenkins-ci.org/display/JENKINS/Job+DSL+Plugin). So he is the best person to explain features, benefits, tips and tricks of this useful plugin. Basically it allows programmatic creation of build jobs using a DSL. Pushing job creation into a script allows to automate, standardize and distribute them across different Jenkins installations.



Jenkins in the Enterprise: Building Resilient CI Infrastructure by Harpreet Singh and Kohsuke Kawaguchi (CloudBees). A presentation of the Jenkins Enterprise solution by CloudBees made by Harpreet and an overview of the future of Jenkins (including a live demo of the Workflow feature (the release 1.0 of this plugin is available since the beginning of this month, according to the original deadline)) made by Kohsuke himself.



Building, Testing & Deploying Android Apps with Jenkins by Christopher Orr (iosphere GmbH).
A nice talk on how to automate the building, testing emulating different devices and deployment of Android applications using Jenkins.  At present time a new automation testing framework for mobile apps (in particular for Android and iOS) called Appium (http://appium.io/) is available. It would be interesting to make a comparison between Appium and the testing frameworks suggested by Christopher in order to understand pros and cons of each approach.


 
Lightweight PaaS for Jenkins CI Environments with Docker by Josef Fuchshuber (QAware GmbH). An introduction to Docker (https://www.docker.com/) followed by a real application of this platform in the deployment of dynamic build slaves for Jenkins and the benefits of this solution.



You can find the slides or the videos of most part of the talks in the CloudBees website.

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