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

Enable Arcade V3 publishing in PR Validation #73221

Open
wants to merge 40 commits into
base: main
Choose a base branch
from

Conversation

JoeRobich
Copy link
Member

@JoeRobich JoeRobich commented Apr 24, 2024

Switch to v3 publishing in order to use publish symbol exclusions. Also, sets a more descriptive build number including the PR author and title.

Example of fancy build number:
image

Test Run: https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=9523427&view=results (microsoft)
Test Insertion: waiting for it (microsoft)

@dotnet-issue-labeler dotnet-issue-labeler bot added Area-Infrastructure untriaged Issues and PRs which have not yet been triaged by a lead labels Apr 24, 2024
"Accept" = "application/vnd.github+json";
"X-GitHub-Api-Version" = "2022-11-28"
}
$buildNumberName = "$(OriginalBuildNumber) - $($pull_request.user.login) - '$($pull_request.title)'"
Copy link
Member Author

Choose a reason for hiding this comment

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

This is a pretty fancy build number. We have to revert it during the Arcade bits and the VS insertions but for most of the build we will show it and we will exit with it being fancy,

Copy link
Member

Choose a reason for hiding this comment

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

ooh, I like it :), will make it easier to find them

@JoeRobich JoeRobich marked this pull request as ready for review May 1, 2024 22:35
@JoeRobich JoeRobich requested review from a team as code owners May 1, 2024 22:35
"Accept" = "application/vnd.github+json";
"X-GitHub-Api-Version" = "2022-11-28"
}
$buildNumberName = "$(OriginalBuildNumber) - $($pull_request.user.login) - '$($pull_request.title)'"
Copy link
Member

Choose a reason for hiding this comment

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

ooh, I like it :), will make it easier to find them

eng/Publishing.props Outdated Show resolved Hide resolved
eng/SymbolPublishingExclusionsFile.txt Outdated Show resolved Hide resolved
eng/SymbolPublishingExclusionsFile.txt Outdated Show resolved Hide resolved
eng/build.ps1 Outdated Show resolved Hide resolved
Comment on lines +75 to +84
- output: artifactsDrop
displayName: 'OptProf - Publish to Artifact Services - ProfilingInputs'
condition: succeeded()
dropServiceURI: 'https://devdiv.artifacts.visualstudio.com'
buildNumber: 'ProfilingInputs/$(System.TeamProject)/$(Build.Repository.Name)/$(SourceBranchName)/$(OriginalBuildNumber)'
sourcePath: '$(Build.SourcesDirectory)\artifacts\OptProf\$(BuildConfiguration)\Data'
toLowerCase: false
usePat: true
accessToken: $(_DevDivDropAccessToken)
retentionDays: 90
Copy link
Member Author

Choose a reason for hiding this comment

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

So currently our official build doesn't use the artifactsDrop output and uses an ArtifactsDrop task instead. Do we want to move it over to match?

Copy link
Member

Choose a reason for hiding this comment

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

Hmm, fine with this way if it works

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Infrastructure untriaged Issues and PRs which have not yet been triaged by a lead
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants