{"push_id":1420471318,"size":1,"distinct_size":1,"ref":"refs/heads/ci-agent-swarm","head":"35e1fd6dec4b9ae4dae03f38232122eb892e52ac","before":"64c6d7b6fade8df14432bdfc44e8bf9fa2fab25e","commits":[{"sha":"35e1fd6dec4b9ae4dae03f38232122eb892e52ac","author":{"name":"Mikael","email":"474f98b881b153898ad9bac97c12047e104089a5@gmail.com"},"message":"Jenkins swarm client\n\nThis commit adds the functionality to connect a Jenkins agent to a Jenkins master with the swarm client.\n\nThe swarm client will run on Jenkins agents as an upstart service.\n\nThe discovery address is hard coded as a temporary measure until we have a fact to resolve.\n\nAt the moment if we wanted to use another version of the swarm client.  We would have to reflect the change in two places with class parameters `$swarm_client_dest` and `$swarm_client_url`.\n\nThere is one manual step where we have to retrieve the api_token for the user we're authenticating against the Jenkins master with.\nTo automate this would mean opening up a potential security hole.\nSee: [jenkins.security.ApiTokenProperty.showTokenToAdmins](https://wiki.jenkins-ci.org/display/JENKINS/Features+controlled+by+system+properties)","distinct":true,"url":"https://api.github.com/repos/alphagov/govuk-puppet/commits/35e1fd6dec4b9ae4dae03f38232122eb892e52ac"}]}
{"actor":{"display_login":"djsd123"}}