We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We need to automate the build and deployment of our nuget packages. Each package needs to have a consistent build number.
We should probably run the dotnet pack command with versioning after each CI build (we can have different versions for PR builds vs master builds).
The deployment to nuget.org should most likely be a separate workflow file as it should be manually triggered once we have a release.
The text was updated successfully, but these errors were encountered:
This article may be a good starting point: https://cloudblogs.microsoft.com/industry-blog/en-gb/technetuk/2019/06/18/perfecting-continuous-delivery-of-nuget-packages-for-azure-artifacts/
Sorry, something went wrong.
This is also a good one: https://intellitect.com/azure-devops-nugets/
It may make sense that our local PR builds push to GitHub Packages and our release builds goes to nuget.org
Successfully merging a pull request may close this issue.
Background
We need to automate the build and deployment of our nuget packages.
Each package needs to have a consistent build number.
We should probably run the dotnet pack command with versioning after each CI build (we can have different versions for PR builds vs master builds).
The deployment to nuget.org should most likely be a separate workflow file as it should be manually triggered once we have a release.
The text was updated successfully, but these errors were encountered: