Jenkins Build Status On Ninja Blocks RGB LED
Nestor v0.1.2 is out and one of its new features is nestor ninja for monitoring Jenkins and displaying the latest build status on Ninja Blocks RGB LED device (if you have a block, it’s the ninja’s eyes).
Here’s a usage example:
export JENKINS_URL=<url>
export NINJABLOCKS_TOKEN=<token_from_https://a.ninja.is/hacking>
nestor ninja
Red for build failure, green for build success, yellow for build warning, and white for unknown status. The yellow light looks quite similar to green, and the white one does look blue-ish.
And the best place to run nestor ninja? On the block itself of course!
ssh ubuntu@ninjablock.local
apt-get install upstart
npm install -g nestor
cat /usr/lib/node_modules/nestor/conf/ninja_upstart.conf > /etc/init/nestor_ninja.conf
vi /etc/init/nestor_ninja.conf # and change JENKINS_URL and NINJABLOCKS_TOKEN values
shutdown -r now
Log messages will then be written to /var/log/nestor_ninja.log
Work: canberra continuous delivery jenkins osdc travel
by Cliffano Subagio
leave a comment
Canberra Workcapade 2011
I went to Canberra this week to attend Open Source Developers Conference 2011 and also to give a talk titled Continuous Delivery Using Jenkins. OSDC ran for 3 days, and was held at Australian National University.
OSDC 2011 was very well organised, much thanks to the organisers: Evan Leybourn, Gavin Jackson, and the volunteers squad. It was an interesting grass roots conference with lots of passionate open source geeks, definitely learned a lot.
Slides from my talk:
Update (24/11/2011): and the video of the talk:
Canberra was still as quiet as ever…
Use Jenkins On Firefox By Talking To Your Mac
I was watching I, Robot the other day, and thought how great it would be to use voice to control Jenkins.
So last night I did a quick read, and then recorded this video.
This used Mac Speech Recognition, so in theory I talked to my Mac, which then opened Jenkins pages on Firefox. Here are the commands:
- ‘Open Jenkins’: opens Jenkins home page (dashboard)
- ‘Build Bob’: builds a project called Bob
- ‘Configure system’: opens Jenkins configuration page
I had to repeat each command 2-3 times because I speak Indonesian-accented English.
Note: I scrolled the page up and down using the trackpad, it could be voice-controlled too actually.
It’s easy to add a command:
- Create a new file in /Users/<username>/Library/Speech/Speakable Items/Application Speakable Items/firefox directory containing:
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>URL</key> <string>http://jenkins-host:8080</string> </dict> </plist>
This format is Mac OS X Property List.
- Save this file as <command>, e.g. Open Jenkins (yes, with the space).
- Open System Preferences -> Speech, and switch Speakable Items on.
- Configure the Listening Method. I set it to Listen continuously with keyword, and keyword is Required before each command. My keyword is VIKI, you know, Virtual Interactive Kinetic Intelligence, from the movie.
I haven’t investigated how much programming can be done on the command file, but this opens up the possibility of mapping Jenkins HTTP API to commands, and we will be able to fully interact with Jenkins using voice.
Then the only thing left to do is… develop an American accent.
Nestor – A Faster And Simpler CLI For Jenkins
It all started because at one point I was using a rather resource-challenged machine running Windows and an Ubuntu VM at the same time, and Firefox froze every so often, rendering Jenkins BuildMonitor and Jenkins web interface useless most of the time. So I looked for an alternative and gave Jenkins CLI a go.
Like most Java applications, Jenkins built-in CLI also suffers from slow start up time (flame suit: ON) due to core Java libraries loading (Kohsuke later told me on #jenkins that there’s also a handshaking process involved). This led me to try Jenkins Remote Access API with curl, which performed significantly faster than Jenkins CLI.
So that’s great, but I have another issue with the fact that Jenkins CLI’s commands start with “java -jar jenkins-cli.jar …”, that’s a finger twister right there, and lengthy curl + URL obviously doesn’t help.
Enter Nestor, a Jenkins CLI written in Node.js that aims to be a faster and simpler alternative to the existing solutions. The catch? Node.js and npm support on Windows is not there yet, so if you managed to run Nestor on Windows please let me know about it. Nestor has been tested and used daily on OS X and Linux.
Simple setup
Install Nestor using npm install -g nestor
Configure the Jenkins instance you want to use using export JENKINS_URL=http://user:pass@host:port/path
Simple usage
Nestor commands are simple, it’s always nestor <action> <param>
To trigger a build
> nestor build studio-bob Job was started successfully
To view a job status
> nestor job studio-bob Status: OK No xml report files found for checkstyle Build stability: 3 out of the last 5 builds failed.
To list the executors
> nestor executor * master idle 39% studio-bob
To view the queue
> nestor queue Queue is empty
To view all jobs status on the dashboard
> nestor dashboard WARN blojsom-bloojm OK jenkins-buildmonitor FAIL studio-ae86 OK studio-bob
Check out Nestor’s GitHub README page for more commands available.
Hopefully that’s simple enough.
Note: The name Nestor was inspired by Captain Haddock’s butler at Marlinspike Hall, not the Argonaut one.
Using Node.js To Discover Jenkins On The Network
I’ve just added a new feature to Nestor to discover Jenkins on the network, and as it turned out, it’s pretty simple to do thanks to Node.js Datagram sockets API (hat tip Paul Querna).
Jenkins has a discovery feature as part of its remote access API where it listens on UDP port 33848, and whenever it receives a message, Jenkins will respond with an XML containing the instance’s URL, version number, and slave port information.
So how do you send a UDP message using NodeJS?
Here’s a sample function adapted from Nestor’s lib/service.js:
function sendUdp(message, host, port, cb) {
var socket = require('dgram').createSocket('udp4'),
buffer = new Buffer(message);
socket.on("error", function (err) {
cb(err);
});
socket.on("message", function (data) {
cb(null, data);
});
socket.send(buffer, 0, buffer.length, port, host, function (err, message) {
if (err) {
cb(err);
}
});
}
For Jenkins discovery purpose, send any message to any hostname on port 33848:
sendUdp('Long live Jenkins!', 'localhost', 33848, function () { ... });
and if there’s any Jenkins instance running on localhost, it will respond with an XML like this:
<hudson> <version>1.414</version> <url>http://localhost:8080</url> <slave-port>12345</slave-port> </hudson>
Simple!
konan cliffano$ nestor discover Jenkins 1.414 running at http://localhost:8080/