The #1 Reason Jenkins Failsby@dan-garfield
2,058 reads
2,058 reads

The #1 Reason Jenkins Fails

by Dan Garfield4mAugust 7th, 2019
Read on Terminal Reader
Read this story w/o Javascript
tldt arrow

Too Long; Didn't Read

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.

Company Mentioned

Mention Thumbnail
featured image - The #1 Reason Jenkins Fails
Dan Garfield HackerNoon profile picture
Dan Garfield

Dan Garfield

@dan-garfield

Chief Open Source Officer and Co-Founder of Codefresh | ArgoProj Maintainer | OpenGitOps Co-Founder

Learn More
LEARN MORE ABOUT @DAN-GARFIELD'S
EXPERTISE AND PLACE ON THE INTERNET.

Share Your Thoughts

About Author

Dan Garfield HackerNoon profile picture
Dan Garfield@dan-garfield
Chief Open Source Officer and Co-Founder of Codefresh | ArgoProj Maintainer | OpenGitOps Co-Founder

TOPICS

THIS ARTICLE WAS FEATURED IN...

Permanent on Arweave
Read on Terminal Reader
Read this story in a terminal
 Terminal
Read this story w/o Javascript
Read this story w/o Javascript
 Lite
L O A D I N G
. . . comments & more!