Convert the build pipeline from Nuke to Fallout - #3234
Conversation
Test Results 37 files ±0 37 suites ±0 2m 38s ⏱️ -15s Results for commit f9d8081. ± Comparison against base commit bde4c01. This pull request removes 10 and adds 8 tests. Note that renamed tests count towards both.♻️ This comment has been updated with latest results. |
Coverage Report for CI Build 27067224620Coverage remained the same at 97.138%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsNo coverage regressions found. Coverage Stats💛 - Coveralls |
Qodana for .NETIt seems all right 👌 No new problems were found according to the checks applied 💡 Qodana analysis was run in the pull request mode: only the changed files were checked Contact Qodana teamContact us at qodana-support@jetbrains.com
|
jnyrup
left a comment
There was a problem hiding this comment.
Just a few remaining mentions of nuke, otherwise looks good to me.
$ git grep -iI nuke
.fallout/build.schema.json: "description": "Disables displaying the NUKE logo"
.fallout/build.schema.json: "default": "Secrets must be entered via 'nuke :secrets [profile]'"
.fallout/build.schema.json: "default": "Secrets must be entered via 'nuke :secrets [profile]'"
.github/dependabot.yml: nuke:
.github/dependabot.yml: - "Nuke*"
.github/workflows/build.yml: - name: Cache .nuke/temp
.github/workflows/build.yml: .nuke/temp
.github/workflows/build.yml: - name: Run NUKE
.github/workflows/build.yml: - name: Run NUKE
Build/Build.cs: - JetBrains ReSharper https://nuke.build/resharper
Build/Build.cs: - JetBrains Rider https://nuke.build/rider
Build/Build.cs: - Microsoft VisualStudio https://nuke.build/visualstudio
Build/Build.cs: - Microsoft VSCode https://nuke.build/vscode
Build/CustomNpmTasks.cs:using NukeDictionaryExtensions = Fallout.Common.Utilities.Collections.DictionaryExtensions;
Build/CustomNpmTasks.cs: NodeDir = RootDirectory / ".nuke" / "temp";
README.md:Or, if you have, the [Nuke tool installed](https://nuke.build/docs/getting-started/installation/):
README.md:`nuke`
README.md:* [Nuke](https://nuke.build/) - Smart automation for DevOps teams and CI/CD pipelines by [Matthias Koch](https://github.com/matkoch)
agents.md:The project uses a [Nuke](https://nuke.build/)-based build system. The build scripts `build.sh` / `build.ps1` / `build.cmd` are thin wrappers around Nuke and support all standard Nuke targets.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
dennisdoomen
left a comment
There was a problem hiding this comment.
Thanks for the review! Addressed all remaining Nuke references in commit 1e60335.
Co-authored-by: Jonas Nyrup <jnyrup@users.noreply.github.com>
Co-authored-by: Jonas Nyrup <jnyrup@users.noreply.github.com>
Summary
This PR converts the build pipeline from Nuke to Fallout.
Changes
Build/_build.csprojto reference Fallout packages (Fallout.Common,Fallout.Components) instead of NukeLibGit2Sharp,NuGet.Packaging,SharpCompress,System.Security.Cryptography.XmlGitVersion.Tool,ReportGenerator,xunit.runner.console,PackageGuard