chore: migrate the build pipeline from NUKE to Fallout - #125
Merged
Conversation
NUKE no longer supports the .NET SDK the build agents install, so CI fails before it reaches any target. This ports the migration the core repository made in Testably/aweXpect#1017. - Rename `.nuke` to `.fallout` and point the Fallout global tool at `Pipeline/Build.csproj` through `BuildProjectFile` in `parameters.json`. - Replace Nuke.Common/Nuke.Components 10.1.0 with Fallout.Common/ Fallout.Components 10.4.0 and rewrite the pipeline namespaces: `Nuke.Common.ProjectModel` becomes `Fallout.Solutions`, everything else `Fallout.Common.*`. - Pin NuGet.Frameworks to 7.9.0: the SDK's MSBuild expects `NuGet.Frameworks 7.9.0.0` while the build host otherwise resolves 6.x transitively, which breaks in-process project evaluation. - Pin the SDK to the 10.0.3xx band in `global.json` and the workflows. `global.json`, the workflow `dotnet-version` lists and the NuGet.Frameworks pin have to be bumped together from now on. - Drop the NUKE enterprise feed handling from the bootstrap scripts and ignore `.fallout/temp/`. Fallout 10.4.0 is the latest listed release; the entire 11.0.x band is unlisted on nuget.org. Verified locally: the pipeline project compiles, `--help` lists every target, and `UnitTests` and `Pack` succeed in Release.
vbreuss
force-pushed
the
chore/migrate-nuke-to-fallout
branch
from
September 4, 2026 17:13
f979d9c to
ce36115
Compare
|
|
This is addressed in release v0.6.0. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
NUKE no longer supports the .NET SDK the build agents install, so CI fails before it reaches any target. This ports the migration the core repository made in Testably/aweXpect#1017.
.nuketo.falloutand point the Fallout global tool atPipeline/Build.csprojthroughBuildProjectFileinparameters.json.Nuke.Common.ProjectModelbecomesFallout.Solutions, everything elseFallout.Common.*.NuGet.Frameworks 7.9.0.0while the build host otherwise resolves 6.x transitively, which breaks in-process project evaluation.global.jsonand the workflows.global.json, the workflowdotnet-versionlists and the NuGet.Frameworks pin have to be bumped together from now on..fallout/temp/.Fallout 10.4.0 is the latest listed release; the entire 11.0.x band is unlisted on nuget.org.
Verified locally: the pipeline project compiles,
--helplists every target, andUnitTestsandPacksucceed in Release.