Fair enough if you've some development environment automation and you want the CI to run it as well so CI is consistent with local development. Don't know exactly what your doing but others(myself included) are using…
The problem is some stuff is a real pain to test with static assertions. Such as I was saying about compilers. It would be a real pain to maintain an expected AST in a unit test, then you'd have to go rework it all if…
I mean... They told you why it takes so long no? the runners come by default with loads of programming languages installed like Rust, Haskell, Node, Python, .Net etc so it sets all that up per user add. I would also…
cringe
Ansible is CaC(Config as Code) not IaC(Infrastructure as Code) they're for different things.
This is what I done, GitHub Actions is basically a command line as a service for my projects. It does nothing but checkout the code, means I can do all the releasing, artefact uploading, compiling & testing etc locally.
I mean all CIs work out of the box, although I have no interest in self hosting CI. Jenkins is probably a bit like Java, technically it is fine. The problem is really where/who typically uses it and as there is so much…
Yes I am seeing what your saying, it can start of simple and people will choose the path of least resistance and you'll end up with a ball of mud eventually. Fortunately I have not come across anything that bad yet. I…
I replaced building/testing etc inside Docker containers to just using Nix. * https://github.com/DeveloperC286/clean_git_history/commit/f8...
Jobs run in parallel, so if you used Make you could have one job called 'formatting' calling 'make check-formatting', one called linting calling ''make check-linting', one called 'compiling' calling 'make compile' etc.
I use to have my Makefile call out and do `docker build ...` and `docker run ...` etc with a volume mount of the source code to manage and maintain tooling versions etc. It works okay, better than a lot of other…
> However it’s really easy to go from a simple shell script running a few commands to something significantly more complex just to do something seemingly simple, like parse a semantic version, make an api call and check…
I don't touch Windows so I would not know. > The same Python testing code runs on all three platforms. I have no objections to Python being used for testing, I use it myself for the end to end tests in my projects. I…
> UV scripts are great for this type of workflow So previously when I have seen Python used as a task runner I think they used UV to call it. Although I don't think they had as a complete solution as your here…
Personally, I have never found the Python as a task runners to be less code, more readable or maintainable.
I was doing something similar when moving from Earthly. But I have since moved to Nix to manage the environment. It is a lot better of a developer experience and faster! I would checkout an environment manager like…
Yes exactly! I am using Nix/Make and I can prompt Claude to use Nix/Make, it uses these local feedback loops and corrects itself sometimes etc.
> Yeah, tends to happen a lot when you hold strong opinions with strong conviction :) Not that it's wrong or anything, but it's highly subjective in the end. Strong opinions, loosely held :) > Typically I see larger…
> Huh? Who cares if the script is .sh, .bash, Makefile, Justfile, .py, .js or even .php? Me, typically I have found it to be a sign of over-engineering and found no benefits over just using shell script/task runner, as…
Just use a task runner(Make, Just, Taskfile) this is what they were designed for.
> If your CI can do things that you can't do locally: that is a problem. Completely agree. > I'm a huge fan of "train as you fight", whatever build tools you have locally should be what's used in CI. That is what I am…
I agree with #2, I meant more if you are calling out to something that is not a task runner(Make, Taskfile, Just etc) or a shell script thats a bit of a smell to me. E.g. I have seen people call out to Python scripts…
[dead]
> For the love of all that is holy, don’t let GitHub Actions > manage your logic. Keep your scripts under your own damn > control and just make the Actions call them! I mean your problem was not `build.rs` here and…
I would disagree with 1. if you need anything more than shell that starts to become a smell to me. The build/testing process etc should be simple enough to not need anything more.
Fair enough if you've some development environment automation and you want the CI to run it as well so CI is consistent with local development. Don't know exactly what your doing but others(myself included) are using…
The problem is some stuff is a real pain to test with static assertions. Such as I was saying about compilers. It would be a real pain to maintain an expected AST in a unit test, then you'd have to go rework it all if…
I mean... They told you why it takes so long no? the runners come by default with loads of programming languages installed like Rust, Haskell, Node, Python, .Net etc so it sets all that up per user add. I would also…
cringe
Ansible is CaC(Config as Code) not IaC(Infrastructure as Code) they're for different things.
This is what I done, GitHub Actions is basically a command line as a service for my projects. It does nothing but checkout the code, means I can do all the releasing, artefact uploading, compiling & testing etc locally.
I mean all CIs work out of the box, although I have no interest in self hosting CI. Jenkins is probably a bit like Java, technically it is fine. The problem is really where/who typically uses it and as there is so much…
Yes I am seeing what your saying, it can start of simple and people will choose the path of least resistance and you'll end up with a ball of mud eventually. Fortunately I have not come across anything that bad yet. I…
I replaced building/testing etc inside Docker containers to just using Nix. * https://github.com/DeveloperC286/clean_git_history/commit/f8...
Jobs run in parallel, so if you used Make you could have one job called 'formatting' calling 'make check-formatting', one called linting calling ''make check-linting', one called 'compiling' calling 'make compile' etc.
I use to have my Makefile call out and do `docker build ...` and `docker run ...` etc with a volume mount of the source code to manage and maintain tooling versions etc. It works okay, better than a lot of other…
> However it’s really easy to go from a simple shell script running a few commands to something significantly more complex just to do something seemingly simple, like parse a semantic version, make an api call and check…
I don't touch Windows so I would not know. > The same Python testing code runs on all three platforms. I have no objections to Python being used for testing, I use it myself for the end to end tests in my projects. I…
> UV scripts are great for this type of workflow So previously when I have seen Python used as a task runner I think they used UV to call it. Although I don't think they had as a complete solution as your here…
Personally, I have never found the Python as a task runners to be less code, more readable or maintainable.
I was doing something similar when moving from Earthly. But I have since moved to Nix to manage the environment. It is a lot better of a developer experience and faster! I would checkout an environment manager like…
Yes exactly! I am using Nix/Make and I can prompt Claude to use Nix/Make, it uses these local feedback loops and corrects itself sometimes etc.
> Yeah, tends to happen a lot when you hold strong opinions with strong conviction :) Not that it's wrong or anything, but it's highly subjective in the end. Strong opinions, loosely held :) > Typically I see larger…
> Huh? Who cares if the script is .sh, .bash, Makefile, Justfile, .py, .js or even .php? Me, typically I have found it to be a sign of over-engineering and found no benefits over just using shell script/task runner, as…
Just use a task runner(Make, Just, Taskfile) this is what they were designed for.
> If your CI can do things that you can't do locally: that is a problem. Completely agree. > I'm a huge fan of "train as you fight", whatever build tools you have locally should be what's used in CI. That is what I am…
I agree with #2, I meant more if you are calling out to something that is not a task runner(Make, Taskfile, Just etc) or a shell script thats a bit of a smell to me. E.g. I have seen people call out to Python scripts…
[dead]
> For the love of all that is holy, don’t let GitHub Actions > manage your logic. Keep your scripts under your own damn > control and just make the Actions call them! I mean your problem was not `build.rs` here and…
I would disagree with 1. if you need anything more than shell that starts to become a smell to me. The build/testing process etc should be simple enough to not need anything more.