{"id":125,"date":"2010-02-26T18:11:20","date_gmt":"2010-02-26T18:11:20","guid":{"rendered":"http:\/\/psyphi.net\/blog\/?p=125"},"modified":"2010-02-26T19:18:26","modified_gmt":"2010-02-26T19:18:26","slug":"configuring-hudson-continuous-integration-slaves","status":"publish","type":"post","link":"https:\/\/psyphi.net\/blog\/2010\/02\/configuring-hudson-continuous-integration-slaves\/","title":{"rendered":"Configuring Hudson Continuous Integration Slaves"},"content":{"rendered":"

Roughly this time last year I set up Hudson<\/a> at the office to do Oxford Nanopore’s continuous integration builds. It’s been a pleasure to roll-out the automated-testing work-ethic for developers and (perhaps surprisingly) there’s been less resistance than I expected. Hudson is a great weapon in the arsenal and is dead easy to set up as a master server. This week though I’ve had to do something new – configure one of our product simulators as my first Hudson slave server. Again this proved to be a doddle – thanks Hudson!<\/p>\n

My slave server is called “device2” – Here’s what I needed to set up on the master (ci.example.net).<\/p>\n

“Manage Hudson” => “Manage Nodes” => “New Node” => node name = “device2”, type is “dumb slave” => number of executors = 1, remote fs root = “\/home\/hudson\/ci”, leave for tied jobs only, launch by JNLP.<\/p>\n

Then on device2:<\/p>\n

adduser hudson\r\nsu hudson\r\ncd\r\nmkdir ci\r\ncd ci\r\nwget http:\/\/ci.example.net\/jnlpJars\/slave.jar<\/code><\/pre>\n
Made a new file \/etc\/init.d\/hudson-slave with these contents:<\/p>\n
#!\/bin\/bash\r\n#\r\n# Init file for hudson server daemon\r\n#\r\n# chkconfig: 2345 65 15\r\n# description: Hudson slave\r\n\r\n. \/etc\/rc.d\/init.d\/functions\r\n\r\nRETVAL=0\r\nNODE_NAME=\"device2\"\r\nHUDSON_HOST=ci.example.net\r\nUSER=hudson\r\nLOG=\/home\/hudson\/ci\/hudson.log\r\nSLAVE_JAR=\/home\/hudson\/ci\/slave.jar\r\n\r\npid_of_hudson() {\r\n    ps auxwww | grep java | grep hudson | grep -v grep | awk '{ print $2 }'\r\n}\r\n\r\nstart() {\r\n    echo -n $\"Starting hudson: \"\r\n    COMMAND=\"java -jar $SLAVE_JAR -jnlpUrl \\\r\n        http:\/\/${HUDSON_HOST}\/computer\/${NODE_NAME}\/slave-agent.jnlp \\\r\n        2>$LOG.err \\\r\n        >$LOG.out\"\r\n    su ${USER} -c \"$COMMAND\" &\r\n    sleep 1\r\n    pid_of_hudson > \/dev\/null\r\n    RETVAL=$?\r\n    [ $RETVAL = 0 ] && success || failure\r\n    echo\r\n}\r\n\r\nstop() {\r\n    echo -n \"Stopping hudson slave: \"\r\n    pid=`pid_of_hudson`\r\n    [ -n \"$pid\" ] && kill $pid\r\n    RETVAL=$?\r\n    cnt=10\r\n    while [ $RETVAL = 0 -a $cnt -gt 0 ] &&\r\n        { pid_of_hudson > \/dev\/null ; } ; do\r\n        sleep 1\r\n        ((cnt--))\r\n    done\r\n\r\n    [ $RETVAL = 0 ] && success || failure\r\n    echo\r\n}\r\n\r\nstatus() {\r\n    pid=`pid_of_hudson`\r\n    if [ -n \"$pid\" ]; then\r\n        echo \"hudson (pid $pid) is running...\"\r\n        return 0\r\n    fi\r\n    echo \"hudson is stopped\"\r\n    return 3\r\n}\r\n\r\n#Switch on called\r\ncase \"$1\" in\r\n    start)\r\n        start\r\n        ;;\r\n    stop)\r\n        stop\r\n        ;;\r\n    status)\r\n        status\r\n        ;;\r\n    restart)\r\n        stop\r\n        start\r\n        ;;\r\n    *)\r\n        echo $\"Usage: $0 (start|stop|restart|status}\"\r\n        exit 1\r\nesac\r\n\r\nexit $RETVAL<\/code><\/pre>\n
chkconfig --add hudson-slave\r\nchkconfig hudson-slave on\r\nservice hudson-slave start<\/code><\/pre>\n
and that’s pretty much all there was to it – refreshing the node-status page on the hudson master showed the slave had registered itself, then reconfiguring one of the existing jobs to be tied to the “device2” slave immediately started assigning jobs to it. Tremendous!<\/p>\n","protected":false},"excerpt":{"rendered":"
Roughly this time last year I set up Hudson at the office to do Oxford Nanopore’s continuous integration builds. It’s been a pleasure to roll-out the automated-testing work-ethic for developers and (perhaps surprisingly) there’s been less resistance than I expected. Hudson is a great weapon in the arsenal and is dead easy to set up … Continue reading “Configuring Hudson Continuous Integration Slaves”<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_uf_show_specific_survey":0,"_uf_disable_surveys":false,"footnotes":""},"categories":[17],"tags":[217,220,218,219],"class_list":["post-125","post","type-post","status-publish","format-standard","hentry","category-sysadmin","tag-ci","tag-configuration","tag-hudson","tag-testing"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t