15 ms·
I think this "lesson" is not lost on many, including those that built and work with Jenkins and plugins. The Jenkins X project moved to a very different approac
by michaelneale 7y ago
I think this "lesson" is not lost on many, including those that built and work with Jenkins and plugins. The Jenkins X project moved to a very different approach, a fresh start.
see https://cd.foundation/ https://cd.foundation/ & https://jenkins-x.io https://jenkins-x.io (it works with Jenkins if you like, but natively uses the new pipelines and no SPOF masters). Might not be for everyone but worth a look.
disclosure: cofounder of cloudbees here (wanted to comment on original article but not able to for some reason on medium).
- chucky_z 7y agoWhy the dependence on Kubernetes everywhere in these new tools?
- michaelneale 7y agowell as far as I know bash and gcc don't depend on kubernetes yet, but that is a good point. It isnt' for everyone (and I wouldn't want to run it myself - GKE or EKS is fine but otherwise.. it seems tough to run). Also this is really a starting point for Jenkins X - I expect options for non kubernetes to be coming.
- michaelneale 7y agoBut to your point (sorry I missed it first) - assuming kubernetes is like assuming an OS, you get to do things like preview apps and other benefits. But if that isn’t for you https://www.cloudbees.com/products/cloudbees-jenkins-distribution https://www.cloudbees.com/products/cloudbees-jenkins-distrib... aims to simplify the Jenkins config.