Add scripts for VSTS to pick PSES branches to include #1498
Conversation
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
| @@ -0,0 +1,11 @@ | |||
| $vstsVariables = @{ | |||
| PSES_BRANCH = '2.0.0' | |||
There was a problem hiding this comment.
why is this set to 2.0.0 vs 1.8.X?
There was a problem hiding this comment.
Because I cherry picked this change from a branch building against 2.0.0. Have changed it to master
rjmholt
force-pushed
the
add-branch-release-tooling
branch
from
3b59e62 to
e3283f7
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PR Summary
Adds scripts to be used by the build to determine what PSES branch to build against.
This means a given branch of the VSCode extension can set the
PSES_BRANCHenvironment variable intools/releaseBuild/setVstsVariables.ps1to determine what branch of EditorServices will get pulled into that build.Quick design consideration: should this instead be expanded out to a JSON or a PSD1 file?
PR Checklist
Note: Tick the boxes below that apply to this pull request by putting an
xbetween the square brackets.Please mark anything not applicable to this PR
NA.WIP:to the beginning of the title and remove the prefix when the PR is ready