.circleci/env.windows.sh

####################################################################################################
# Set bazel configuration for CircleCI runs.
####################################################################################################
cp "${PROJECT_ROOT}/.circleci/bazel.windows.rc" ".bazelrc.user";

# Override the `PATH` environment variable so that the windows-nvm NodeJS version
# always has precedence over potential existing NodeJS versions from the image.
setPublicVar PATH "/c/Program Files/nodejs/:$PATH"

# Expose the Bazelisk version. We need to run Bazelisk globally since Windows has problems launching
# Bazel from a node modules directoy that might be modified by the Bazel Yarn install then.
setPublicVar BAZELISK_VERSION \
    "$(cd ${PROJECT_ROOT}; node -p 'require("./package.json").devDependencies["@bazel/bazelisk"]')"
ci: make windows circleci job more robust and use git bash (#45431) It is totally fine, and expected to use Git Bash for running Bazel on Windows. In fact this is the most common setup for Bazel on Windows and it's unrealistic to run without it. This allows us to remove the old/legacy Powershell setup from CI which is also quite flaky sometimes and does not reproduce how Bazel is used on windows-users dev machines. PR Close #45431 2022-03-23 20:40:28 +01:00			`####################################################################################################`
			`# Set bazel configuration for CircleCI runs.`
			`####################################################################################################`
build: setup remote execution through shared command (#47537) Sets up remote execution through a shared command. PR Close #47537 2022-09-24 09:09:53 +00:00			`cp "${PROJECT_ROOT}/.circleci/bazel.windows.rc" ".bazelrc.user";`
ci: improve stability of windows bazel CI job (#45431) Improves stability of the Windows Bazel CI job by installing Bazelisk globally. Also makes the environment helpers more convenient by evaluating the variable assignments directly, simplifying some Bash logic. PR Close #45431 2022-03-24 20:23:53 +01:00
build: attempt to avoid nodejs version flakiness in `test_win` job (#48326) The `test_win` job is occasionally failing where a super old NodeJS version is used even though we installed a proper one with `nvm`. It's unclear how the CircleCI windows VMs differ here, it's coming up rarely and is hard to reproduce when SSH-ing into VMs. Our best guess is that the existing NodeJS version from the container/image is super old and somehow takes precedence over the NVM-managed NodeJS version. This could happen due to bad ordering in the `$PATH` environment variable, or NVM not properly being wired up there. We attempt to fix this by always setting `$PATH` to the NVM symlink directory manually- with highest priority. PR Close #48326 2022-12-02 14:48:14 +00:00			# Override the `PATH` environment variable so that the windows-nvm NodeJS version
			`# always has precedence over potential existing NodeJS versions from the image.`
			`setPublicVar PATH "/c/Program Files/nodejs/:$PATH"`
ci: improve stability of windows bazel CI job (#45431) Improves stability of the Windows Bazel CI job by installing Bazelisk globally. Also makes the environment helpers more convenient by evaluating the variable assignments directly, simplifying some Bash logic. PR Close #45431 2022-03-24 20:23:53 +01:00
			`# Expose the Bazelisk version. We need to run Bazelisk globally since Windows has problems launching`
			`# Bazel from a node modules directoy that might be modified by the Bazel Yarn install then.`
			`setPublicVar BAZELISK_VERSION \`
build: setup remote execution through shared command (#47537) Sets up remote execution through a shared command. PR Close #47537 2022-09-24 09:09:53 +00:00			`"$(cd ${PROJECT_ROOT}; node -p 'require("./package.json").devDependencies["@bazel/bazelisk"]')"`