Fallout

Build automation for C#/.NET — write your CI/CD pipelines in plain C#, debug them locally, and share build steps across repositories. The hard-fork successor to NUKE.

Read the docs → View on GitHub

Quick start

Already have the .NET SDK? You can be running a Fallout build in under a minute.

Install the global tool

dotnet tool install Fallout.GlobalTool --global

Scaffold a build in any repository

fallout :setup

Run it

fallout

That's a real C# console app — open the build project in your IDE and you've got code completion, refactoring, and a debugger across your whole pipeline.

Why Fallout

Builds are C#

Your pipeline is a regular console app — full IDE support, real types, refactoring, and a debugger. No YAML to fight with.

Debug locally

Tedious commit-and-pray cycles cost real time. Step through your build on your machine before it ever touches CI.

CI/CD generation

Emit provider configs (GitHub Actions and friends) from your build definition so the CI YAML stays in sync with the code that drives it.

Coming from NUKE?

Fallout is the hard-fork successor to NUKE — same C#-first ethos, under new maintenance. The migration guide walks you through it: docs.fallout.build/docs/migration/from-nuke. The short version: dotnet tool install -g Fallout.Migrate and run fallout-migrate in your existing NUKE repo.