120
Jenkins was invented b/c an engineer “got tired of incurring the wrath of his team every time his code broke the build.” (graphite.dev)
submitted 2 years ago by to c/programming@programming.dev
27 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 6 points 2 years ago (13 children)

I like Jenkins a lot - but I'd love it if somebody could give it a bit of a facelift. It looks and feels very aged at this point.

  • permalink
  • fedilink
  • source
  • hideshow 13 child comments
    •
  • [–] 28 points 2 years ago (10 children)

    I have to say, pretty much every CI/CD tool, build automation or whatever you want to call it, sucks.

    Somehow they all manage not to offer boilerplate actions since that would be too restrictive, yet they also stand in your way if you want to have advanced features.

    I often end up writing pipeline steps/jobs thinking "how is that not already built-in?".

    And my absolutely biggest pain point: why the fuck is there not a single tool that lets me execute pipelines locally? Why do I have to have 200 commits all saying a variation of "pipeline test"?

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

    I agree so, so much; and I've been saying similar things for years.

    But I recognize that it's probably a hard problem. For one thing, auth is almost never going to work the same way in CI as it does locally.

    ...still, though, I feel like there could be some much nicer tooling here.

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

    The sentiment of the first half of your comment is the cause of the problem you describe in the second half. Why /should/ the CI tool have any "steps" built in? Use a task runner, or script in your repo for any task you expect CI to do. Configure CI to run the same command you would run locally.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago

    I totally agree, with some caveats:

    1. It can make the UI much nicer (though I agree there are probably better ways to do it, e.g. native support for letting the program output determine the UI).
    2. Sometimes you need to run different things on different machines/OSes, and it's easier if you have separate steps there.
  • permalink
  • fedilink
  • source
  • parent