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

The #1 Reason Jenkins Fails

tldt arrow
Read on Terminal Reader🖨️

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

Learn More
LEARN MORE ABOUT @DAN-GARFIELD'S EXPERTISE AND PLACE ON THE INTERNET.
react to story with heart

RELATED STORIES

L O A D I N G
. . . comments & more!
Hackernoon hq - po box 2206, edwards, colorado 81632, usa