Running Serverless Continuous Delivery by Viktor Farcic at JBCNConf'19
Channel: Barcelona Jug
Date: 2019-07-31

Running applications for continuous delivery is a massive waste of resources. Think about it. We spend gigabytes of RAM for running Jenkins, Bamboo, Team City, or whichever tool we're using. And yet, those tools are often sitting idle inside our cluster, waiting to eventually receive a webhook notifying them that something should be done. As a result, resources are wasted when those tools are idle, and they are slow when under heavy load. If we add agents to the mix, we can quickly end up with hundreds of unused servers, and yet not have enough. What if we could run our tools only when we need them? What if we could scale them to any number of replicas to accommodate the increase in the number of builds, and scale them down to zero when there are no new commits? What if we can do all that with a single command? The answer to those and quite a few other questions is to go serverless with our continuous delivery tools. Jenkins X happens to do just that. It is a cloud-native Kubernetes-first solution that embraced a serverless model for managing our pipelines.
http://www.jbcnconf.com/2019/infoTalk.html?id=5cd1f98438da161cb0381424