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.

Sign up for GitHub

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

Jump to bottom

SpecificBuildNumber must not be specified along with DropPath #855

Open
RikkiGibson opened this issue Nov 16, 2020 · 0 comments
Open

SpecificBuildNumber must not be specified along with DropPath #855

RikkiGibson opened this issue Nov 16, 2020 · 0 comments
Assignees
@RikkiGibson

Comments

@RikkiGibson
Copy link
Contributor

In many of our AzDo pipelines we have an artifact for Roslyn which we download via the AzDo mechanisms to save time (by reading it in using the DropPath argument):

image

But we also have a SpecificBuildNumber property:

image

Giving a SpecificBuildNumber that contradicts the artifacts in the DropPath causes a really bad failure mode, where the title of the PR and the diff of changes shows one changeset, and the version numbers that are actually being inserted can be completely unrelated. See https://dev.azure.com/devdiv/DevDiv/_git/VS/pullrequest/288025?view=discussion for example.

tagging @JoeRobich @ryzngard
@RikkiGibson RikkiGibson self-assigned this Jan 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@RikkiGibson RikkiGibson

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@RikkiGibson