Add a note with workaround Azure Artifacts source when packages are m…#14368
Open
arkoppan wants to merge 1 commit intoMicrosoftDocs:mainfrom
Open
Add a note with workaround Azure Artifacts source when packages are m…#14368arkoppan wants to merge 1 commit intoMicrosoftDocs:mainfrom
arkoppan wants to merge 1 commit intoMicrosoftDocs:mainfrom
Conversation
…issing in Package drop down list. Added notes on handling package truncation in Azure Artifacts source when using Feeds with many packages. We are getting cases related to this issue since May 2022 or earlier. There was a fix released for more than 15k feeds but the issue is related to number of packages in the feed. Please reach out if you need reference to related bug and IcMs.
Contributor
|
@arkoppan : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
Contributor
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
Contributor
There was a problem hiding this comment.
Pull request overview
Adds documentation to help users troubleshoot missing packages in the Azure Artifacts artifact source picker for classic release pipelines when feeds contain many packages.
Changes:
- Added a NOTE describing package list truncation for feeds with many packages.
- Documented two workarounds: promoting packages into a view, or providing the package ID via REST API.
Comment on lines
+162
to
+164
| > When using Feeds with 1000 packages or more, you may see that the packages in Package drop down in Azure Artifacts source may be truncated after certain packages. | ||
| > To work around this issue, create a new Custom View and [promote](https://learn.microsoft.com/en-us/azure/devops/artifacts/feeds/views?view=azure-devops&tabs=nuget%2Cnugetserver22%2Cpowershell) packages to that view. And then in the Release pipeline, specify the View in the Azure Artifact source. | ||
| > Or you can you can provide the package ID, which you can find using the instructions [here](https://learn.microsoft.com/en-us/rest/api/azure/devops/artifacts/artifact-details/get-packages?view=azure-devops-rest-5.0). |
Comment on lines
+163
to
+164
| > To work around this issue, create a new Custom View and [promote](https://learn.microsoft.com/en-us/azure/devops/artifacts/feeds/views?view=azure-devops&tabs=nuget%2Cnugetserver22%2Cpowershell) packages to that view. And then in the Release pipeline, specify the View in the Azure Artifact source. | ||
| > Or you can you can provide the package ID, which you can find using the instructions [here](https://learn.microsoft.com/en-us/rest/api/azure/devops/artifacts/artifact-details/get-packages?view=azure-devops-rest-5.0). |
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
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.
…issing in Package drop down list.
Added notes on handling package truncation in Azure Artifacts source when using Feeds with many packages.
We are getting cases related to this issue since May 2022 or earlier. There was a fix released for more than 15k feeds but the issue is related to number of packages in the feed. Please reach out if you need reference to related bug and IcMs.