Analysis updated 2026-07-03
Replace a YAML build pipeline with a typed, debuggable C# script that compiles, tests, and publishes a .NET project in one command.
Automatically generate GitHub Actions, GitLab CI, and Azure Pipelines YAML from a single NUKE C# build definition to keep all platforms in sync.
Share common build targets across multiple .NET repositories using NUKE's component system to avoid duplicating pipeline logic.
Debug a failing CI step locally by running the exact NUKE target in your IDE with breakpoints instead of pushing and waiting for a remote run.
| nuke-build/nuke | lay295/twitchdownloader | pwntester/ysoserial.net | |
|---|---|---|---|
| Stars | 3,727 | 3,723 | 3,723 |
| Language | C# | C# | C# |
| Setup difficulty | easy | easy | moderate |
| Complexity | 3/5 | 2/5 | 3/5 |
| Audience | ops devops | general | researcher |
Figures from each repo's GitHub metadata at analysis time.
NUKE is a build automation system for .NET and C# projects. Build automation means writing code that controls how a software project gets compiled, tested, packaged, and deployed, rather than doing those steps by hand each time. Most build systems make developers write their automation logic in YAML files or shell scripts, which do not come with code completion, easy debugging, or the other tools C# developers are used to. NUKE lets you write that same automation in C# instead, as a regular console application. Because a NUKE build script is just C# code, developers can use their normal IDE features: autocomplete, refactoring tools, type checking, and step-by-step debugging. The build is organized into named targets, which are individual steps like compiling, running tests, or publishing a package. You can declare which targets depend on others, and NUKE figures out the correct order to run them. Parameters can be injected from environment variables, command-line arguments, or CI/CD system variables, all through the same mechanism. One feature the README highlights is CI/CD configuration generation. Rather than maintaining separate YAML files for GitHub Actions, TeamCity, GitLab CI, Azure Pipelines, and other services, NUKE can generate those files automatically from the C# build definition. This means you write the logic once and the configuration for each platform is produced from it, reducing the chance of inconsistencies between platforms. NUKE also handles some common practical problems in .NET builds: abstracting path separator differences between Windows and Linux, giving access to .NET solution and project file data from within the build script, and supporting shared build components that can be reused across multiple repositories. The project is open source under the MIT license and available as a NuGet package. It has active community channels on Slack and Discord.
NUKE is a build automation framework for .NET that lets you write compile, test, and deploy pipelines in C# instead of YAML, with full IDE support, type checking, debugging, and automatic CI/CD config generation for GitHub Actions, Azure Pipelines, and more.
Mainly C#. The stack also includes C#, .NET, NuGet.
Use freely for any purpose, including commercial use, with no conditions beyond keeping the copyright notice.
Setup difficulty is rated easy, with roughly 30min to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
Verify against the repo before relying on details.