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
[–] 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