Explore Three alternatives to using Makefiles.
Can these be used to describe some of the CI/CD steps that are usually encoded in jenkinsfiles? This would make it possible to test (some of) the steps locally instead of having to push and wait for a Jenkins pipeline to run. I.e. faster feedback loop.
https://taskfile.dev/
"Task" is a task runner / build tool that aims to be simpler and easier to use than, for example, GNU Make.
https://github.com/casey/just
"just" is a handy way to save and run project-specific commands.
"just" is a command runner, not a build system, so it avoids much of make's complexity and idiosyncrasies. No need for .PHONY recipes!
Maybe https://github.com/erichs/composure also falls in this area. I have looked at it before, and installed it years ago, but never gotten around to really giving it a chance.
Explore Three alternatives to using Makefiles. Can these be used to describe some of the CI/CD steps that are usually encoded in jenkinsfiles? This would make it possible to test (some of) the steps locally instead of having to push and wait for a Jenkins pipeline to run. I.e. faster feedback loop.
https://taskfile.dev/ "Task" is a task runner / build tool that aims to be simpler and easier to use than, for example, GNU Make.
https://github.com/casey/just "just" is a handy way to save and run project-specific commands. "just" is a command runner, not a build system, so it avoids much of make's complexity and idiosyncrasies. No need for .PHONY recipes!
https://github.com/adriancooney/Taskfile This repo uses plain Bash to implement a very simple task runner. Could this be enough, if you don’t need a full build system? This has also been covered in https://www.youtube.com/watch?v=SdmYd5hJISM
┆Card is synchronized with this Github issue by Unito