Just about everyone has used the size_t type - and everybody and their grandmothers know what the type means of course! The usual answers I get to ‘tell me what size_t is without Googling it’ is;
It is the parameter type for malloc to allocate memory! It is a platform dependent 32/64 bit unsigned integer type! It is what size_type in all the C++ std template hell is! (ok I made this one up - but fuck me the size_type lark really annoys me in the std code.
So I previously installed Jenkins on my Raspberry Pi 2, and ran my first job through Jenkins. The final obvious step was to get another build node to connect to my Jenkins server so that workload can be offloaded from the Raspberry Pi 2 to another device.
The lovely folks over at Imagination Technologies sent me a MIPS Creator CI20 board a while back, and this seemed like the perfect node to add to my new Jenkins build farm!
So in my last post Installing Jenkins on Raspberry Pi 2 I took us through the steps it took me to get a Jenkins server running on my Raspberry Pi 2 - but I didn’t actually run any jobs on the Raspberry Pi 2! Time to rectify.
So I decided to build doboz - a really awesome little compression/decompression library written by Attila Áfra. I first forked it from HG -> Git, and fired it up onto my GitHub here.
So I’ve always wanted to roll my own home continuous integration (CI) server - I use Jenkins as my main CI at work (having used Atlassian’s Bamboo and the hideousness that is buildbot in the past), so I thought I may as well start there.
I previously tried to get Jenkins running on my Raspberry Pi B+ - but the single core and general slowness of the device just meant it wasn’t feasible.
