fix(ci): work around CI Windows git failure MONGOSH-660 #750
Conversation
This file contains 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
For some reason, Windows builds started failing recently. The windows-64-vs2019-small image, the Node.js version, the npm version, the git version, and the package-lock.json all remained the same in that period, so it is unclear what exactly caused this. While a full investigation would likely be interesting, that’s not easy with Evergreen’s current capabilities. However, fixing this seems possible by explicitly adding the git binaries (including libexec ones) to the PATH, so let’s do that for now.
mcasimir
approved these changes
Mar 31, 2021
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.
For some reason, Windows builds started failing recently.
The windows-64-vs2019-small image, the Node.js version,
the npm version, the git version, and the package-lock.json
all remained the same in that period, so it is unclear
what exactly caused this.
While a full investigation would likely be interesting,
that’s not easy with Evergreen’s current capabilities.
However, fixing this seems possible by explicitly adding
the git binaries (including libexec ones) to the PATH,
so let’s do that for now.