The #1 Reason Jenkins Fails

Written by dan-garfield | Published 2019/08/07
Tech Story Tags: jenkins | codefresh | kubernetes | cicd | devops | continuous-delivery | continuous-integration | k8s

TLDR While Jenkins has been both loved and hated for being DevOps duct tape, every user knows there are plenty of issues to deal with. The biggest issue may surprise you because it creates a cascade effect. Sharing libraries operate in a global space, different tooling can easily conflict. It’s one of the reasons dev teams decide to go rogue and spin up their own instances. Because Codefresh offers both isolation at the step level, as well as role-based access controls and other security features, teams are typically able to work off of shared instances.via the TL;DR App

no story

Written by dan-garfield | Chief Open Source Officer and Co-Founder of Codefresh | ArgoProj Maintainer | OpenGitOps Co-Founder
Published by HackerNoon on 2019/08/07