There were a number of build automation systems for the .net ecosystem. All had their own pros which helped many developers in the build teams. Developers in the other teams also had chances to work in the build automation systems. But some build systems needed full-time build engineers to code and run those systems.
As a web developer, I too had a chance to work in the build automation systems,
- FinalBuilder - with a GUI, it was too easy to prepare and run the builds.
- PowerShell - build system with PowerShell scripts was powerful yet complex to write.
- Cake (C# Make) - simple, easy to set up, and with a lot of extensions scripting with C#.
BUT, now I had the opportunity to use Nuke.Build for my build system and I am obsessed heavily with it that I love it so much.
Comparing all these 4 build systems, from my point of view, I would recommend Nuke. We would not need a separate build team while using Nuke as it is coupled with your project itself. You would be able to debug Nuke targets in your own IDE.
Here is a sample nuke project for your reference. https://github.com/vengi83644/nuke-build-sample
Similar blog: https://pknopf.com/post/2019-03-10-you-dont-need-cake-anymore-the-way-to-build-dotnet-projects-going-forward/