Cake VS NUKE

Cake (C# Make) is a cross-platform build automation system with C# DSL.

This is why 90-99% of our builds are done with Cake. It isolates all of it and you can run the build locally if you want.

A good starting point of you want to get started with Cake is our website at https://cakebuild.net/

I don't think it will get too much confusion, but there is a build system called Cake: https://cakebuild.net/

You may use other tools too: psake, make, cake, fake or any other *ake you are familiar with. I look at them as a tools that make build tasks behind simple commands and help me answer: How did I run that code again?

NAnt was quite a popular build tool used by projects of all sizes targeting .NET Framework on Windows. I have written many complex build systems using NAnt in the past. But XML based DSL was quite clunky to use and maintain. Besides, it was always a daunting task to explain to a new dev on the team. With .NET Core/.NET becoming a cross-platform framework, CAKE and FAKE gained a lot of adoption providing a C# and F# based DSL for build tasks accordingly.

Cake (C# Make) - simple, easy to set up, and with a lot of extensions scripting with C#.

I got the example and the answer I needed on this thread: https://github.com/cake-build/cake/discussions/3564

For those not familiar with it, Cake is a build automation system with a C#-based DSL. It is based on the concept of tasks, which are small units of work, like restoring packages, building, or testing, which can have dependencies on, or trigger, other tasks.

Just a note: there's already a very active community of the same name for the build utility Cake.

Today, we will continue our journey with Nuke by adding new targets to the solution presented in Nuke: Deploy ASP.NET Web App to Azure. This time, we will deploy our application to a local Kubernetes cluster using Helm.

In this post, we will explore the benefits of Nuke and its most common features as we deploy a web app to Azure. Our goal is to achieve a flexible, maintainable, automated build process.

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.