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

Upgrade NuGet.Client arcade version to 6.0 #10646

Closed
crummel opened this issue Mar 9, 2021 · 4 comments
Closed

Upgrade NuGet.Client arcade version to 6.0 #10646

crummel opened this issue Mar 9, 2021 · 4 comments
Assignees
Labels
Engineering Productivity Partner:DotNet Resolution:NotABug This issue appears to not be a bug Type:Engineering product/infrastructure work/not a customer bug/feature/DCR

Comments

@crummel
Copy link

crummel commented Mar 9, 2021

Arcade-powered source-build requires Arcade 6.0 or higher. NuGet.Client will need to be upgraded to support ArPow.

@erdembayar
Copy link
Contributor

@crummel
Hi. Thank you for your contribution. It looks you already have PR created. Can you self assign ticket for yourself?

@nkolev92
Copy link
Member

@erdembayar
He can't assign, he's not part of the org.

@zivkan zivkan added Type:Engineering product/infrastructure work/not a customer bug/feature/DCR Engineering Productivity Partner:DotNet and removed Product:VS.Client Tenet:Compliance Tenet:Reliability Crashes, hangs etc. labels Mar 10, 2021
@zivkan
Copy link
Member

zivkan commented Mar 10, 2021

Also the pull request explicitly says that it won't work/can't be tested until this issue is complete. The PR does not fix this issue.

@crummel I've looked into onboarding to the Arcade SDK about a year ago, but due to NuGet's heavy build customization in our build/* directory, adding the Arcade SDK broke our build and seemed to require a lot of effort to get working. In addition, from my very limited knowledge of Arcade, it appears to be fundamentally incompatible with all our release scripts, so we'll have to rewrite those too. And this means that our ability to service existing releases that are still in LTS will be significantly impacted.

What's the timeframe that onboarding onto the Arcade SDK is required? Will DncEng/SourceBuild teams be creating pull requests to onboard NuGet.Client onto Arcade, or do you require us to change our schedule to do this work ourselves?

@aortiz-msft aortiz-msft added the Resolution:NotABug This issue appears to not be a bug label Mar 11, 2021
@aortiz-msft
Copy link
Contributor

Closing as per last comment from zivkan.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Engineering Productivity Partner:DotNet Resolution:NotABug This issue appears to not be a bug Type:Engineering product/infrastructure work/not a customer bug/feature/DCR
Projects
None yet
Development

No branches or pull requests

6 participants