| I think that's a fairly big statement. I worked with Robert and told him I wasn't a fan of the shared libraries approach because it abstracts the workflow away from the team, when the reality is we want more people to understand the pipeline, not less. Jenkins itself is a bit of a hodgebodge of legacy crap. - Plugins that do next to nothing. Hard to reproduce this. - Inability to run locally; gives you the rope to hang yourself. - Bit of a security mess - Upgrade and admin story historically pretty poor; lack of infrastructure as code, etc. Conflicting versions when you restore. - Unclear story on relying on state. Why isn't my build environment clean? Jenkins is actually a pretty good tool, especially when you use it well. But once you're been around the block a couple of times and deal with teams failing with a tool, for a variety of reasons, you start to wonder if maybe the complexity of the tool itself is the culprit. |