-
Notifications
You must be signed in to change notification settings - Fork 9
[CI] Publish: NuGet #366
New issue
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
base: main
Are you sure you want to change the base?
[CI] Publish: NuGet #366
Conversation
1993835
to
fc85c5c
Compare
fc85c5c
to
b4f35fb
Compare
b4f35fb
to
14737b5
Compare
ee4607b
to
4be1c27
Compare
eng/pipelines/official.yml
Outdated
allowPackageConflicts: false | ||
publishPackageMetadata: true | ||
- task: 1ES.PublishNuget@1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want a single approval for both AzDO and NuGet, or do we want separate approvals?
Are there cases where we want to publish to only one?
eng/pipelines/official.yml
Outdated
allowPackageConflicts: false | ||
publishPackageMetadata: true | ||
publishFeedCredentials: DotNet-SDK-Workloads-NuGet |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TODO: We need to create a Service Connection to NuGet with an API Key with push access
Note: need to figure out how to get an api key still |
…either to AzDO or NuGet. Still some info missing for NuGet to work.
Extends #362 to add new stage for publishing to NuGet