VS Target Branch/Channel props & OptProf Schedule now reflect Dev18 VS release cadence#7163
Open
donnie-msft wants to merge 3 commits intodevfrom
Open
VS Target Branch/Channel props & OptProf Schedule now reflect Dev18 VS release cadence#7163donnie-msft wants to merge 3 commits intodevfrom
donnie-msft wants to merge 3 commits intodevfrom
Conversation
Contributor
|
Since this PR is changing CI as it modifies YML files, please verify that you've addressed how this change should apply to release branches. Either:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bug
Fixes: https://github.com/NuGet/Client.Engineering/issues/3650
Description
Fixes OptProf on 18.4 or higher by changing the VS Target Branch/Channel to the new naming pattern for Dev18.
Dev will use the latest main VS build, while the release branch will use the public Insiders VS build.
Changes the triggers so that only LTS branches and dev branch run OptProf.
Going forward, only the branches that support VS's LTS release cycle need OptProf.
I also expect we'll stop seeing OptProf failures we've seen with
7.x.xrelease branches since this change stops queuing all7.x.xrelease branches for OptProf.PR Checklist
Added testsLink to an issue or pull request to update docs if this PR changes settings, environment variables, new feature, etc.