Skip to content

Conversation

@webwarrior-ws
Copy link
Contributor

Split the job deployReleaseBinaries in two:

  • One called packReleaseBinaries, that just uploads stuff as artifact.
  • Another one called publishReleaseBinaries, that uploads nuget packages to nuget.org.
  • The 2 integration tests run after packReleaseBinaries is green.
  • After the 2 integration tests pass, then publishReleaseBinaries runs (using packReleaseBinaries' artifacts, with the download-artifact action).

Split the job deployReleaseBinaries in two:
- One called packReleaseBinaries, that just uploads stuff as
artifact.
- Another one called publishReleaseBinaries, that uploads nuget
packages to nuget.org.
- The 2 integration tests run after packReleaseBinaries is
green.
- After the 2 integration tests pass, then
publishReleaseBinaries runs (using packReleaseBinaries'
artifacts, with the download-artifact action).
@webwarrior-ws webwarrior-ws force-pushed the ci-split-deploy-binaries branch from 784fff5 to 7a2d22f Compare December 4, 2025 10:14
@knocte knocte merged commit 6e434a6 into fsprojects:master Dec 4, 2025
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants