NUKE VS moon

Is it similar to Nuke?

Another thing I could recommend is to use something like Nuke build system to automate more complex tasks that aren't good fit for csproj using C# code (for example - publishing and zipping self-contained release of some service for specific platform using current date and time or commit hash as version number).

testcontainers and https://github.com/dotnet/Docker.DotNet are on my to-do list to try out, but just like with something like https://nuke.build/ i can't see the value other than that the config would be c# instead of some flavour of yaml.

We started using https://nuke.build/. Early days so can’t comment too much but it seems good so far.

I think you're giving a really bad example of what consumers should expect from open-source projects. This year I reworked the whole website, released several versions, did a huge chunk of development, and spoke at 5 events (with travel). This is the first significant gap in almost 6 years of continuous development. Maybe it's hard to imagine, but also maintainers sometimes face severe issues in their life. Comments like this don't make it any better.

Posting this here because I think only .NET people use Nuke (https://nuke.build/) to manage their build.

(for context - I'm not interested in first class node support)

This seems pretty cool. I particularly like how 'gradual' it seems to be relative to things like Bazel, i.e. you can take some shell scripts and migrate things over. I did have a play and hit an initial problem around project caching I think, which I raised at [0].

One comment, from the paranoid point of view of someone who has built distributed caching build systems before is that your caching is very pessimistic! I understand why you hash outputs by default (as well as inputs), but I think that will massively reduce hit rate a lot of the time when it may not be necessary? I raised [1].

As an aside, I do wish build systems moved beyond the 'file-based' approach to inputs/outputs to something more abstract/extensible. For example, when creating docker images I'd prefer to define an extension that informs the build system of the docker image hash, rather than create marker files on disk (the same is true of initiating rebuilds on environment variable change, which I see moon has some limited support for). It just feels like language agnostic build systems saw the file-based nature of Make and said 'good enough for us' (honorable mention to Shake, which is an exception [2]).

[0] https://github.com/moonrepo/moon/issues/637

There are many tools like Lerna, Nx, Turborepo, Moon, Rush, and Bazel, to name a few. Today, we'll be using Turborepo, as it's lightweight, flexible, and easy to use.

You should give moon a try: https://moonrepo.dev/