Updates to official build pipeline #6423
Conversation
|
Builds cancelled since they do not test these changes. |
| Daily NuGet builds of the project are also available in our Azure DevOps feed: | ||
|
|
||
| > [https://pkgs.dev.azure.com/dnceng/public/_packaging/MachineLearning/nuget/v3/index.json](https://pkgs.dev.azure.com/dnceng/public/_packaging/MachineLearning/nuget/v3/index.json) | ||
| > [https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-libraries/nuget/v3/index.json](https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-libraries/nuget/v3/index.json) |
There was a problem hiding this comment.
This changing the internal feed location. right? I am just asking as sometimes I share that with other parties.
There was a problem hiding this comment.
Yes, we discussed this with the arcade folks and they said we shouldn't maintain our own Artifacts feed. They wanted us to use the common dotnet-libraries feed just like other libraries similar to us. For example: https://github.com/dotnet/command-line-api/blob/main/README.md
The actual change that moved the feed was in de79b8a#diff-70773eb1e66297b0e83e4f7d57285bec90b978c662da1c90a5fcbcb1bc534688L346
If we wanted to bring back publishing to the other feed we can, but my goal is to get us as much as possible off "special cases"
|
|
ghost
locked as resolved and limited conversation to collaborators
2 participants
We were using the wrong values for the TSA tool (we were using Arcade's rather than our own). This has been fixed and tested with https://dev.azure.com/dnceng/internal/_build/results?buildId=2034373&view=results.
I also updated the link to nightly packages, now that we use Arcade templates / darc we're publishing to the dotnet-libraries feed.