10 years of blogging?!?

Edit: So this was attempt 2 of this post. Thank goodness for Google cache! Don’t start a migration to a new server whilst still updating your site 🙂

So after having my WordPress install nag at me to update for ages, I finally got round to it. Also took the opportunity to clean up my FTP directory which has had bits and pieces lying around for years.

With this update, we now have a new theme, some nice random header images and Archives! I took a quick look at it and realised I’ve been blogging off and on for the last decade! I remember starting back on Blogger back in the day and then migrating to WordPress. Those blog posts from back then didn’t migrate that well, hence the numbers as post titles. And I also think I’m possibly missing a few weeks or months of the very start of my blogging foray… :-(

From WordPress was the migration to Drupal where I blogged periodically for a number of years and then the painful migration back. It’s just a little bit crazy to know I’ve still basically got 10 years of posts intact! There’s a couple of years in between where the posting is sporadic, but hopefully I’ll keep this guy more up to date with my ramblings, musings and thoughts.

Objective C, Xcode revisted

It’s been a few years since I’ve written in Objective C for iOS and used Xcode, and I must say it has changed/matured a lot since then.

The first time, thrown into the middle of an intense project, was a crash course in the intricacies of the language and IDE. And being mainly a Java front end dev back then with very limited C experience was interesting to say the least.

But I’m glad to say that alot has changed since then, and for the better. After giving some documentation a once over and playing around with things, lots of the oddities that I saw coming to the language as a Java developer have now been improved.

The biggest things for me (so far) I think were:

  • Automatic synthesizing of properties.
  • Automatic reference counting (ARC). It puzzled me that writing code for the OS had memory management, but you had to manually manage for iOS.
  • Setting up your project with unit tests is a breeze.

There are other things, and if you haven’t looked at it in a while you might be pleasantly surprised.

Monitor your Jenkins build with an Arduino (and some Java code)

So I got my hands on an Arduino kit a while back but hadn’t played around with it much. Whilst I await for some books to arrive so I can learn basic electronics and circuits (am a developer without engineering/electronics background…) I thought it’d be fun to see if I could write something simple that could be useful in my day to day job as a Java developer.

One of the tools we use is Jenkins and whilst we get emails and check the Jenkins Dashboard to see if a build has failed,  developers often have a tendency to not check their emails or check Jenkins to see what the state of the build is… As a result it may be hours or even a few days before someone realises the build is not passing…

So it seemed fitting to write some code to get a LED light to blink if the build is failing. To do this you’ll need the following:

  • Jenkins with the build you want to monitor setup
  • Arduino (I’m using an Uno)
  • A LED (though for test purposes if you’re using an Uno pin 13 has a LED built in which should be sufficient)
  1. Wire up your LED to one of the pins or do what I did and use the built in LED on pin 13.
  2. Write some code in your language of choice to grab the build status from Jenkins and send it serially to the Arduino. I chose to grab the status as JSON, but there are other options available. I used Java and the Spring Framework to schedule a process to run every 5 seconds to grab the Jenkins status and send it across to the Arduino with the main grunt work being the code below: [sourcecode language=”java”]
    package com.delineneo.processor;

    import com.delineneo.communication.SerialCommunicator;
    import org.springframework.beans.factory.annotation.Autowired;
    import org.springframework.scheduling.annotation.Scheduled;
    import org.springframework.stereotype.Component;
    import org.springframework.web.client.RestTemplate;

    import java.io.IOException;

    import static org.apache.commons.lang.StringUtils.contains;

    * Created by IntelliJ IDEA.
    * User: deline
    * Date: 2/03/12
    * Time: 8:33 PM
    public class JenkinsStatusProcessor {
    private static final String JENKINS_URL = "http://localhost:8080/job/JenkinsStatus/api/json" ;
    private static final String SUCCESS_BUILD_COLOR = "blue";
    public static final char BUILD_FAIL = ‘0’;
    public static final char BUILD_SUCCESS = ‘1’;

    private RestTemplate restTemplate;
    private SerialCommunicator serialCommunicator;

    public void process() {

    String jsonString = restTemplate.getForObject(JENKINS_URL, String.class);

    boolean buildSuccess = isBuildSuccessful(jsonString);
    try {
    serialCommunicator.send(buildSuccess ? BUILD_SUCCESS : BUILD_FAIL);
    } catch (IOException e) {

    private boolean isBuildSuccessful(String jsonString) {
    if (contains(jsonString, SUCCESS_BUILD_COLOR)) {
    return true;
    return false;

    public void setRestTemplate(RestTemplate restTemplate) {
    this.restTemplate = restTemplate;

    public void setSerialCommunicator(SerialCommunicator serialCommunicator) {
    this.serialCommunicator = serialCommunicator;

    In the process method we grab the status as JSON using Spring’s RestTemplate then search for the build status colours in the string. Blue represents success and I treat any other colour (yellow and red are the other ones) as a failure. We then send either a ‘0’ or ‘1’ for fail or success respectively.

    You might wonder why we send a char instead of a boolean… Serial write to the Arduino is as an int or byte array, and on the Arduino side read is done either as an int or a char. For example sending ‘A’ will be received via the Arduino as either the char ‘A’ or the int value 65 (the ascii value). This post on bildr gives you a bit more info on why one might choose to read values as and int instead of a char.

  3. Write some code for the Arduino to process the received data and set the LED to flashing if the build has failed. The code below listens on the serial port:
    [sourcecode language=”cpp”]
    /* JenkinsStatus will turn the LED at pin 13 on/off depending
    * on the value serially read.
    const int BUILD_SUCCESS = 49;
    int inByte;
    int currentPinValue = 0;

    void setup() {
    pinMode(13, OUTPUT);

    void loop() {
    if (Serial.available() > 0) {
    inByte = Serial.read();
    if (inByte == BUILD_SUCCESS) {
    digitalWrite(13, LOW);
    } else{
    digitalWrite(13, HIGH);
    } else {
    currentPinValue = digitalRead(13);
    if (currentPinValue == HIGH) {
    digitalWrite(13, LOW);
    digitalWrite(13, HIGH);

    In the loop if there’s data to be read we read it then determine if what state the LED on pin 13 needs to be in. The pin needs to be LOW (i.e. off) if the build is passing and HIGH (on) otherwise. Additionally, if there is no data to be read we want to keep the LED in a flashing state if it was set to HIGH (last read indicated build had failed).

So that’s pretty much the long short of it, the full code is available on my Git repo – https://github.com/deline/JenkinsStatus

Some thoughts on how JenkinsStatus could be improved:

  • Allow config of Jenkins details via properties files
  • Allow more than one Jenkins job to be monitored
  • Put in more LEDs for other states