Skip to content

Onboarding to V3 publishing #6052

Merged
epananth merged 2 commits intomasterfrom
v3-publish
Jan 21, 2021
Merged

Onboarding to V3 publishing #6052
epananth merged 2 commits intomasterfrom
v3-publish

Conversation

@epananth
Copy link
Copy Markdown
Member

Fixes #

Context

Onboarding to V3 publishing.
Link to what is V3 -> https://github.com/dotnet/arcade/blob/master/Documentation/CorePackages/Publishing.md#what-is-v3-publishing-how-is-it-different-from-v2

Changes Made

Testing

CI build - https://dev.azure.com/devdiv/DevDiv/_build/results?buildId=4391278&view=results
Promotion pipeline - https://dev.azure.com/devdiv/DevDiv/_build/results?buildId=4391300&view=results

Notes

Hardcoding of BUILD_REPOSITORY_URI is temporary fix. This will be reverted once this is fixed dotnet/arcade#6827

@epananth
Copy link
Copy Markdown
Member Author

Asset manifest sample

image

Copy link
Copy Markdown
Member

@benvillalobos benvillalobos left a comment

Choose a reason for hiding this comment

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

Mostly LGTM. So the permanent change here really just setting PublishingVersion to 3 in Publishing.props, and all other changes are temp workarounds to get that to work right?

- ${{ if and(eq(parameters.runAsPublic, 'false'), ne(variables['System.TeamProject'], 'public'), notin(variables['Build.Reason'], 'PullRequest')) }}:
- task: NuGetAuthenticate@0

- task: PowerShell@2
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

My understanding has typically been that anything under eng/common is "stuff arcade owns". Will this be overridden if arcade bumps up a version?

Presumably the fix would be in far before we even do that, but I'm curious.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

This fix will block arcade update till I get the other fix out. I am going to be working on it next week. I will have to coordinate with the arcade-services roll out. I will keep you posted on that.

Comment thread .vsts-dotnet.yml
targetType: 'inline'
script: |
Write-Host "Overwriting BUILD_REPOSITORY_URI."
Write-Host "##vso[task.setvariable variable=BUILD_REPOSITORY_URI;]https://dnceng@dev.azure.com/dnceng/internal/_git/dotnet-msbuild"
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Was BUILD_REPOSITORY_URI being used before?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

It is used when generating the asset manifest and during publishing build assets...

Copy link
Copy Markdown
Member

@benvillalobos benvillalobos left a comment

Choose a reason for hiding this comment

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

LGTM. We're going to have to stop taking arcade updates until the temporary solution gets a permanent fix. We shouldn't have a problem with that, considering we've been on 1.0 until now.

One thing that could potentially break us is the signing issue we've had in the past that required us to take an arcade update.

@epananth epananth merged commit cb0a95f into master Jan 21, 2021
@Forgind Forgind deleted the v3-publish branch December 6, 2021 17:49
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.

On boarding Msbuild to V3

3 participants