561
Who is this "Jenkins" and what now has broken him? (programming.dev)
submitted 3 years ago by to c/programmer_humor@programming.dev
67 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 161 points 3 years ago (5 children)

I know this is a meme, but just in case someone doesn't actually know. CI saves literally thousands upon thousands of dev hours a year, even for small teams.

  • permalink
  • fedilink
  • source
  • hideshow 10 child comments
    •
  • [–] 38 points 3 years ago (3 children)

    As annoying as it is when someone else breaks the CI pipeline on me, it is utterly invaluable for keeping the vast majority of commits from being able to break other people (and from you breaking others). I can't imagine not having some form of CI to preventing merging bad code.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 8 points 3 years ago (1 child)

    You should have seen my last job.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 3 years ago

    Hah, or my current one. Before we had CI you just directly committed to master (on SVN). It was incredible how unstable our build was. It broke basically everyday. Then one of the senior back end guys got promoted to architect and revamped the whole thing. Probably saved the company tens of millions dollars in man hours, at the very least.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 4 points 3 years ago

    Even better is when you restrict merges to trunk/main/master/develop (or whatever you call it) to only happen from the CI bot *after all tests (including builds for all supported platforms) pass. Nobody else breaks the CI pipiline, because breaking changes just don't merge. The CI pipeline can test itself!

  • permalink
  • fedilink
  • source
  • parent
  • [–] 37 points 3 years ago

    And a lot of users' frustration, especially on more niche platforms (Linux, ARM, etc.) - things look much better on release when the code have been regularly compiled and, hopefully tested, on all platforms, not just the one the lead developer uses.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 17 points 3 years ago (1 child)

    It wouldn't surprise me if this meme was made by an ops guy.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 8 points 3 years ago (1 child)

    Ops loves CI systems, if the artifact doesn't come from Jenkins (or friends) it simply doesn't exist to us.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 7 points 3 years ago (1 child)

    Probably also causes lots of hours of maintenance and troubleshooting...but it's a net gain in the end.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 28 points 3 years ago (1 child)

    I can't even imagine not having a ci pipeline anymore. Having more than a single production architecture target complete with test sets, Security audits, linters, multiple languages, multiple hour builds per platform... hundreds to thousands of developers... It's just not possible to even try to make software at scale without it.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •