46fe8fb8b4
This has a couple benefits: - we now use a .bazelversion file rather than package.json to pin the version of bazel we want. This means even if you install bazel on your computer rather than via yarn, you'll still get a warning if your bazel version is wrong. - you no longer end up downloading three copies of bazel due to bugs in both npm and yarn where they download all tarballs before checking the metadata to see which are usable on the local platform. - bazelisk correctly handles the tools/bazel trick for wrapping functionality, which we want to use to instrument developer build latencies PR Close #36078
57 lines
3.8 KiB
PowerShell
57 lines
3.8 KiB
PowerShell
# Install Bazel pre-reqs on Windows
|
|
# https://docs.bazel.build/versions/master/install-windows.html
|
|
# https://docs.bazel.build/versions/master/windows.html
|
|
# Install MSYS2 and packages
|
|
choco install msys2 --version 20180531.0.0 --no-progress --package-parameters "/NoUpdate"
|
|
C:\tools\msys64\usr\bin\bash.exe -l -c "pacman --needed --noconfirm -S zip unzip patch diffutils git"
|
|
|
|
# Add PATH modifications to the Powershell profile. This is the win equivalent of .bash_profile.
|
|
# https://docs.microsoft.com/en-us/previous-versions//bb613488(v=vs.85)
|
|
new-item -path $profile -itemtype file -force
|
|
# Paths for nodejs, npm, yarn, and msys2. Use single quotes to prevent interpolation.
|
|
# Add before the original path to use msys2 instead of the installed gitbash.
|
|
Add-Content $profile '$Env:path = "${Env:ProgramFiles}\nodejs\;C:\Users\circleci\AppData\Roaming\npm\;${Env:ProgramFiles(x86)}\Yarn\bin\;C:\Users\circleci\AppData\Local\Yarn\bin\;C:\tools\msys64\usr\bin\;" + $Env:path'
|
|
# Environment variables for Bazel
|
|
Add-Content $profile '$Env:BAZEL_SH = "C:\tools\msys64\usr\bin\bash.exe"'
|
|
|
|
# Get the bazelisk version devdep and store it in a global var for use in the circleci job.
|
|
$bazeliskVersion = & ${Env:ProgramFiles}\nodejs\node.exe -e "console.log(require('./package.json').devDependencies['@bazel/bazelisk'])"
|
|
# This is a tricky situation: we want $bazeliskVersion to be evaluated but not $Env:BAZELISK_VERSION.
|
|
# Formatting works https://stackoverflow.com/questions/32127583/expand-variable-inside-single-quotes
|
|
$bazeliskVersionGlobalVar = '$Env:BAZELISK_VERSION = "{0}"' -f $bazeliskVersion
|
|
Add-Content $profile $bazeliskVersionGlobalVar
|
|
|
|
# Remove the CircleCI checkout SSH override, because it breaks cloning repositories through Bazel.
|
|
# See https://circleci.com/gh/angular/angular/401454 for an example.
|
|
# TODO: is this really needed? Maybe there's a better way. It doesn't happen on Linux or on Codefresh.
|
|
git config --global --unset url.ssh://git@github.com.insteadOf
|
|
|
|
|
|
####################################################################################################
|
|
# Decrypt GCP Credentials and store them as the Google default credentials.
|
|
####################################################################################################
|
|
mkdir ${env:APPDATA}\gcloud
|
|
openssl aes-256-cbc -d -in .circleci\gcp_token -md md5 -out "$env:APPDATA\gcloud\application_default_credentials.json" -k "$env:CIRCLE_PROJECT_REPONAME"
|
|
|
|
####################################################################################################
|
|
# Set bazel configuration for CircleCI runs.
|
|
####################################################################################################
|
|
copy .circleci\bazel.windows.rc ${Env:USERPROFILE}\.bazelrc
|
|
|
|
####################################################################################################
|
|
# Install specific version of node.
|
|
####################################################################################################
|
|
choco install nodejs --version 12.14.1 --no-progress
|
|
|
|
# These Bazel prereqs aren't needed because the CircleCI image already includes them.
|
|
# choco install yarn --version 1.16.0 --no-progress
|
|
# choco install vcredist2015 --version 14.0.24215.20170201
|
|
|
|
# We don't need VS Build Tools for the tested bazel targets.
|
|
# If it's needed again, uncomment these lines.
|
|
# VS Build Tools are needed for Bazel C++ targets (like com_google_protobuf)
|
|
# choco install visualstudio2019buildtools --version 16.1.2.0 --no-progress --package-parameters "--add Microsoft.VisualStudio.Workload.VCTools --add Microsoft.VisualStudio.Component.VC.Tools.x86.x64 --add Microsoft.Component.VC.Runtime.UCRTSDK --add Microsoft.VisualStudio.Component.Windows10SDK.17763"
|
|
# Add-Content $profile '$Env:BAZEL_VC = "${Env:ProgramFiles(x86)}\Microsoft Visual Studio\2019\BuildTools\VC\"'
|
|
# Python is needed for Bazel Python targets
|
|
# choco install python --version 3.5.1 --no-progress
|