-
Notifications
You must be signed in to change notification settings - Fork 510
Fix release build pipeline #3286
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
Conversation
From commit:
|
f5b94aa
to
7425226
Compare
targetType: filePath | ||
filePath: ./vscode-powershell/tools/releaseBuild/setVstsVariables.ps1 | ||
|
||
# TODO: Remove this when satisfied with added trigger. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rjmholt This TODO
bit us good.
Ok so the next preview still has the incorrect version field in the PSD1 file, but that's bug PowerShell/PowerShellEditorServices#1455, I confirmed the DLLs are correct and double-checked the build IDs that were included by the pipeline:
|
db09af9
to
6a025b2
Compare
@rjmholt I pulled the version bump out, I'd like to just merge this, and then do the release. |
6a025b2
to
d74fe49
Compare
A backlog task of removing the `findPsesBuild` script and associated logic caused us to end up with a release with the wrong artifacts. The tagged PSES build was partially succeeded, which the download task then ignored as the trigger, and instead of failing, fell back to this script which gave it the latest fully succeeded build (an old version of PSES). That PSES build was only partially successful because the "Install PowerShell Daily" step failed due to a transient network error, and so this was intentionally ignored as it did not affect the build. Or so we thought.
d74fe49
to
30ef07d
Compare
Fixes #3282.