Skip to content

Conversation

@amanasifkhalid
Copy link
Contributor

@amanasifkhalid amanasifkhalid commented May 2, 2024

This is the first of multiple PRs to replicate @eduardo-vp's work of merging commits needed to transition the release/6.0-staging branch to 1ES pipeline templates. Because this branch and main have diverged quite a bit, I found it safer to manually merge each change by hand, rather than relying on git cherry-pick. As such, this PR probably warrants extra scrutiny...

Official build: https://dev.azure.com/dnceng/internal/_build/results?buildId=2448493&view=results

cc @agocke @jkoritzinsky

@ghost ghost added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label May 2, 2024
@amanasifkhalid amanasifkhalid added area-Infrastructure and removed needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels May 2, 2024
@dotnet-policy-service
Copy link
Contributor

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

@amanasifkhalid amanasifkhalid force-pushed the release/6.0-staging branch from 964d141 to 0d5c19b Compare May 3, 2024 22:57
@amanasifkhalid
Copy link
Contributor Author

/azp run runtime

@azure-pipelines
Copy link

Azure Pipelines failed to run 1 pipeline(s).

@amanasifkhalid amanasifkhalid changed the title Test Backport #92296 and #92438 to release/6.0-staging May 10, 2024
@amanasifkhalid amanasifkhalid marked this pull request as ready for review May 10, 2024 01:41
@amanasifkhalid
Copy link
Contributor Author

Failures in public CI are known

@amanasifkhalid
Copy link
Contributor Author

ping @agocke (sorry, I didn't realize Jeremy is out of office at the moment)

Copy link
Member

@agocke agocke left a comment

Choose a reason for hiding this comment

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

LGTM. FYI, if the PGO build is broken, we probably won't find the issue until it flows up the stack. There's nothing to do about that, it's just the way it works.

@amanasifkhalid
Copy link
Contributor Author

Thank you!

LGTM. FYI, if the PGO build is broken, we probably won't find the issue until it flows up the stack. There's nothing to do about that, it's just the way it works.

I see, I'll keep this in mind.

Copy link
Member

@jeffschwMSFT jeffschwMSFT left a comment

Choose a reason for hiding this comment

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

approved. we can treat this as tell mode, merge when ready

cc @carlossanlop

@amanasifkhalid amanasifkhalid added the Servicing-approved Approved for servicing release label May 13, 2024
@amanasifkhalid amanasifkhalid merged commit e50e868 into dotnet:release/6.0-staging May 13, 2024
@amanasifkhalid amanasifkhalid deleted the release/6.0-staging branch May 13, 2024 18:22
@github-actions github-actions bot locked and limited conversation to collaborators Jun 14, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

area-Infrastructure Servicing-approved Approved for servicing release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants