3 ms·
I've indeed used Jenkins. For all my professional uses, it served perfectly well. Newer releases come with pipeline and k8s support etc., so I'm not of the opin
by penguin_booze 2y ago
I've indeed used Jenkins. For all my professional uses, it served perfectly well. Newer releases come with pipeline and k8s support etc., so I'm not of the opinion that just being ancient is a disqualifier.
- gsaslis 2y agoagreed. Jenkins has suffered from a lot of problems - plugin maintenance across version upgrades being key - but it has also overcome a lot of these problems. It gets criticism just for being... "old". But it is an automation server that is as battle-tested as they come! Also, being old gives it a huge advantage: you can bet you won't need a major rewrite of your pipelines in a couple of years when e.g. GitLab sells, or Microsoft decides GH actions aren't so free (or fast) any more, etc.
- Aeolun 2y agoJust being ancient is not, but it shines through in every single thing that’s there. Building the pipelines, configuring the jobs. If I compare the ergonomics if Github Actions and Jenkins it’s light and day. For me anyway. If you like jenkins I won’t stop you from using it ;)