Great post. I've seen first hand the problems that occur with all the uncontrolled 'state' in Jenkins installations when something goes wrong... lots of manual

Great post. I've seen first hand the problems that occur with all the uncontrolled 'state' in Jenkins installations when something goes wrong... lots of manual work! It's like moving Jenkins towards a static website model where you can always get back to a known state quickly and easily. At hyper.sh we've been working to take this a step further by providing fast starting (couple of seconds), secure and highly-parallelized on-demand CI worker nodes. We started with Buildbot (released yesterday: https://blog.hyper.sh/serverless-ci-hyper-docker-integration-for-buildbot.html https://blog.hyper.sh/serverless-ci-hyper-docker-integration...) and the Jenkins plugin is coming up next. That makes a dream situation whereby you have a Jenkins master that can be easily restored from version control and all workers are created on-demand and billed per second meaning that there is no worker node maintenance at all and you only pay when you're building. We're calling it 'Serverless CI'. Would love to talk to you about this further. You can find contact details on the website if interested!