Note

Fork-Hinweis (fglang. Packages)*

Dies ist ein Fork von nuke-build/nuke. Veröffentlicht wird unter dem fglang.-Präfix auf NuGet.org, um Namens-Kollisionen mit dem Original zu vermeiden.

Installation: dotnet tool install -g fglang.Nuke.GlobalTool

Anpassungen ggü. Upstream:

• Package-IDs auf fglang.* umgestellt (Nuke.Common → fglang.Nuke.Common, etc.)
• Sicherheitsupdates: System.Security.Cryptography.Xml 9.0.0 → 10.0.7 (CVE-2026-26171, CVE-2026-33116), Scriban 6.2.1 → 7.1.0 (kritische CVEs), NuGet.Packaging 6.12.1 → 7.3.1 (GHSA-g4vj-cjjj-v7hg, CWE-345), diverse Patch-/Minor-Bumps
• Major-Updates: Microsoft.CodeAnalysis 4.12 → 5.3, Microsoft.Build 18.0.2 → 18.4.0, coverlet 6 → 10, Microsoft.ApplicationInsights 2 → 3, YamlDotNet 16 → 17, Microsoft.SourceLink.GitHub 8 → 10
• Eigener GitHub-Actions-Workflow nuget-release.yml für NuGet.org-Deployment (Trigger: GitHub Release oder manuell)
• Code-Fix für Microsoft.Build.Framework.AbsolutePath-Kollision in CodeGenerationTask.cs

---

The AKEless Build System for C#/.NET

Table of Contents

• Elevator Pitch
• Example
• Build Status
• Technology Sponsors

Elevator Pitch

Solid and scalable CI/CD pipelines are an essential pillar for being competitive and creating a great product. But why are most of us a little afraid of touching YAML files and don't even dare to look at build scripts? Much of this is because C# developers are spoiled with a great language and smart IDEs, and they don't like missing their buddy for code-completion, ease of debugging, refactorings, and code formatting.

NUKE brings your build automation to an even level with every other .NET project. How? It's a regular console application allowing all the OOP goodness! Besides, it solves many common problems in build automation, like parameter injection, path separator abstraction, access to solution and project models, and build step sharing across repositories. NUKE can also generate CI/CD configurations (YAML, etc.) that automatically parallelize build steps on multiple agents to optimize throughput!

For more information check out our documentation or visit our community ...

Example

Build Status

NUKE builds and tests itself on several CI/CD services, which helps to ensure a working integration with those systems. At the same time, the individual configuration files serve as examples for the generation experience:

Build Server	Status	Platform	Configuration
TeamCity		Win	settings.kts
GitHub Actions		Win / Ubuntu / macOS	continuous.yml
GitLab CI		Ubuntu	.gitlab-ci.yml
Azure Pipelines		Win / Linux / macOS	azure-pipelines.yml
AppVeyor		Win / Ubuntu	appveyor.yml

Technology Sponsors

Thanks to JetBrains for providing licenses for Rider and access to a TeamCity Cloud instance, which both make open-source development a real pleasure!

Thanks to SignPath for providing free code signing service and to the SignPath Foundation for a free code signing certificate.