About nine months ago, the author requested to transfer to the team responsible for the company’s CI tooling. Recognizing that CI was hindering productivity, the author wanted to help improve it and have a positive impact. However, the current CI system in Jenkins had several problems, including unversioned and difficult-to-edit configurations. The author’s team considered switching to Gitlab CI or upgrading to Jenkins 2. Jenkins 2 seemed like a good fit since it supported declarative pipelines and allowed for better control over the environment. However, using Jenkins came with its own set of problems, including high indirection, low discoverability, and an incomplete and unintuitive interface. Overall, the author found using Jenkins as a CI tool to be an unpleasant experience.
http://twitchard.github.io/posts/2019-06-21-life-is-too-short-for-jenkins.html