Skip to content
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

[vs17.8] disallow inserting pkgs twice in VS insertion #11152

Open
wants to merge 1 commit into
base: vs17.8
Choose a base branch
from

Conversation

JanProvaznik
Copy link
Member

@JanProvaznik JanProvaznik commented Dec 16, 2024

Fixes #11136
will propagate via mergeflow

Context

This prevents wrong behavior of the VS insertion with an override for edge cases.

Changes Made

Fail on package conflicts when pushing them to feeds and add an override parameter which skips the pushing stage

Testing

https://devdiv.visualstudio.com/DefaultCollection/DevDiv/_build/results?buildId=10716305&view=results

Notes

@JanProvaznik JanProvaznik changed the title [vs17.8] disallow inserting twice in insertion by default [vs17.8] disallow inserting pkgs twice in VS insertion Dec 16, 2024
@JanProvaznik JanProvaznik requested review from JanKrivanek and a team December 16, 2024 16:08
@@ -56,6 +56,10 @@ parameters:
default: 183
type: number
displayName: 'Drop Retention Days (do not set to < 90)'
- name: SkipUploadingPackages
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you elaborate on why you prefer to have this granularity, instead of an input that directly controls allowPackageConflicts?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I did not see a strong reason for either option. This seemed a tad more clear for the pipeline user and as a bonus it saves like 30s of the pipeline execution.

Copy link
Member

@JanKrivanek JanKrivanek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is helpful - thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants