Add allowPackageConflicts support to DotNetCoreCLI@2#21917
Open
GABRIELNGBTUC wants to merge 2 commits intomicrosoft:masterfrom
Open
Add allowPackageConflicts support to DotNetCoreCLI@2#21917GABRIELNGBTUC wants to merge 2 commits intomicrosoft:masterfrom
allowPackageConflicts support to DotNetCoreCLI@2#21917GABRIELNGBTUC wants to merge 2 commits intomicrosoft:masterfrom
Conversation
…eCLIV2 push command (#2) * Add --skip-duplicate support (allowPackageConflicts) to DotNetCoreCLIV2 push command Co-authored-by: GABRIELNGBTUC <132353744+GABRIELNGBTUC@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: GABRIELNGBTUC <132353744+GABRIELNGBTUC@users.noreply.github.com>
allowPackageConflicts / --skip-duplicate support to DotNetCor…allowPackageConflicts support to DotNetCoreCLI@2
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.
Context
Describe the context or motivation for this PR. Include links to any related Azure DevOps Work Items or GitHub issues.
📌 How to link to ADO Work Items
Today, the recommended way to use the nuget CLI is to use the command "dotnet nuget" since it is cross-platform and no longer requires "mono". A lot of the parameters from the
NugetCommand@2have a 1:1 match inDotNetCoreCLI@2, however the ability to skip duplicates and avoid errors when receiving a 429 Conflict is missing. This pull request aim at allowing to use the parameterallowPackageConflictsinDotNetCoreCLI@2#20981
Task Name
DotNetCoreCLI@2
Description
Update the task
DotNetCoreCLI@2to allow the use of the parameterallowPackageConflictsfromNugetCommand@2when usingDotNetCoreCLI@2withpushas the commandRisk Assessment (Low / Medium / High)
Low
Change Behind Feature Flag (Yes / No)
No as the risk is low. However, it could be if required.
Tech Design / Approach
Documentation Changes Required (Yes/No)
Yes.
https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/reference/dotnet-core-cli-v2?view=azure-pipelines
Unit Tests Added or Updated (Yes / No)
Yes
Additional Testing Performed
List all other tests performed (manual or automated, including integration, regression, scenario tests, etc.).
Logging Added/Updated (Yes/No)
No logging was added.
Telemetry Added/Updated (Yes/No)
No telemetry was added.
Rollback Scenario and Process (Yes/No)
No rollback scenario was planned.
Dependency Impact Assessed and Regression Tested (Yes/No)
No dependency were changed
Checklist