Publish each feed independently and keep each package in its own folder#2910
Merged
Conversation
nohwnd
force-pushed
the
nohwnd-fix-publish-package-folders
branch
from
July 19, 2026 08:18
7aca244 to
8d6239f
Compare
When a publish fails I want to grab the exact built package from the pipeline artifact and upload it to psgallery, nuget or choco by hand. So put each target's package in its own folder under tmp: tmp/nuget.org and tmp/chocolatey for the signed nupkg, and tmp/PSGallery/Pester stays the folder we publish to the gallery. Also keep going when a feed fails instead of aborting on the first error. Before this a failed gallery push skipped nuget and choco. Now each push runs in its own try/catch, the failures are collected, and the build fails at the end listing which feeds to redo by hand. And drop the gallery capture from #2780. The gallery is published from the module folder, not a nupkg, so that captured package was never something we publish. 🤖
nohwnd
force-pushed
the
nohwnd-fix-publish-package-folders
branch
from
July 19, 2026 08:22
8d6239f to
6f783ae
Compare
nohwnd
changed the title
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.
When a publish fails I want to grab the exact built package from the pipeline artifact and upload it to psgallery, nuget or choco by hand. Two changes for that.
Each package in its own folder. So the right one is easy to grab from the artifact:
tmp/PSGallery/Pester/tmp/nuget.org/Pester.<version>.nupkgtmp/chocolatey/Pester.<version>.nupkgNuGet.org and Chocolatey get the identical signed package, so I pack once and copy. The pack input stays
tmp/nuget(the nuspec globs it), only the output nupkg moves into the per-target folder, so the nuspec does not change.Keep going when a feed fails. Before this a failed gallery push aborted the script (
ErrorActionPreference = 'Stop') and nuget and choco were never attempted. Now each push runs in its own try/catch, the failures are collected, and the build fails at the end listing which feeds to redo by hand. The artifact is published onsucceededOrFailed(), so the packages are there even when the run is red.Also drops the gallery capture from #2780. The gallery is published from the module folder, not a nupkg, so that captured package was never something we publish.
Verified
release.ps1parses. Not run end to end, that needs the signing vault and the publish keys.🤖