Releases · aspect-build/bazel

24 Aug 21:12

alexeagle

6.2.0

f6344ff

6.2.0 plus Remote Output Service Latest

Latest

https://github.com/bazelbuild/bazel/releases/tag/6.2.0
plus bazelbuild#12823

Binaries built with

linux-x86_64

USE_BAZEL_VERSION=6.2.0 bazel build -c opt --stamp src:bazel --embed_label 6.2.0-aspect.1 --incompatible_strict_action_env=true
cp bazel-bin/src/bazel bazel-6.2.0-linux-x86_64
shasum bazel-6.2.0-linux-x86_64 > bazel-6.2.0-linux-x86_64.sha256

darwin-x86_64

USE_BAZEL_VERSION=6.2.0 bazel build -c opt --stamp src:bazel --embed_label 6.2.0-aspect.1 --incompatible_strict_action_env=true
cp bazel-bin/src/bazel bazel-6.2.0-darwin-x86_64
shasum bazel-6.2.0-darwin-x86_64 > bazel-6.2.0-darwin-x86_64.sha256

Assets 6

21 Dec 17:11

alexeagle

6.0.0

c8f783b

6.0.0 plus Remote Output Service

https://github.com/bazelbuild/bazel/releases/tag/6.0.0

plus

bazelbuild#12823

Binaries built with

bazel build -c opt --stamp src:bazel --embed_label 6.0.0-aspect.1 --incompatible_strict_action_env=true
cp bazel-bin/src/bazel bazel-6.0.0-linux-x86_64
shasum bazel-6.0.0-linux-x86_64 > bazel-6.0.0-linux-x86_64.sha256

Assets 4

14 Sep 22:28

gregmagolan

6.0.0-pre_20220823_1_aspect

9621d3f

6.0.0-pre_20220823_1_aspect

This release is based off of the 6.0.0-pre.20220823.1.1 tag with a cherry pick of bazelbuild@eb6ba2b from bazelbuild#16272.

The goal is to have a bazel client that can work with symlinks on RBE.

binaries built with

bazel build -c opt --stamp src:bazel --embed_label 6.0.0-pre.20220823.1-aspect --incompatible_strict_action_env=true

Assets 6

23 Aug 22:39

alexeagle

6.0.0-aspect1

cabf36a

6.0.0-aspect1

This release is based on this branch #3

https://github.com/aspect-build/bazel/compare/a2e9f6e401c3fea92a6d515083553ffefdafc24a..cabf36a6142dadaf59cc180b04d69090b4530598

The goal is to have a bazel client that can work with symlinks on RBE.

linux binary built with:

bazel build -c opt --stamp src:bazel --embed_label 6.0.0-pre.20220630.1-symlink --action_env=BAZEL_DO_NOT_DETECT_CPP_TOOLCHAIN=1 --incompatible_strict_action_env=true --incompatible_enable_cc_toolchain_resolution

darwin binary built with:

bazel build -c opt --stamp src:bazel --embed_label 6.0.0-pre.20220630.1-symlink --incompatible_strict_action_env=true

Assets 8

19 Jan 08:58

f0rmiga

5.0.0rc4

7c52020

Release 5.0.0rc4 (2022-01-13) with 7c520204

This is the 5.0.0rc4 release, cherry-picking 7c52020.

This release was produced by the following script:

build.sh

#!/bin/bash

set -o errexit -o pipefail

version="$1"

set -o nounset

if [ -z "${version}" ]; then
    >&2 echo "ERROR: missing version. Usage: $0 <version>. E.g. $0 5.0.0rc4"
    exit 1
fi

git_root="$(git rev-parse --show-toplevel)"
out_dir="/tmp/bazel_build_output"
executable_name="bazel-${version}-linux-x86_64"

mkdir -p "${out_dir}"

rm -rf "${executable_name}"
rm -rf "${executable_name}.sha256"

docker_args=(
    --volume="${git_root}":/workspace/bazel
    --volume="${out_dir}:${out_dir}"
    --volume=/var/run/docker.sock:/var/run/docker.sock
    --volume="${HOME}/.npm:/home/.npm"
    --workdir=/workspace/bazel
    --publish=3000:3000
)

docker run "${docker_args[@]}" -i --rm --entrypoint=/bin/bash --user=root bazel:4.2.2 <<EOF
apt-get install --yes software-properties-common
add-apt-repository ppa:openjdk-r/ppa
apt-get update
apt-get install --yes openjdk-11-jdk
su ubuntu
bazel --output_user_root="${out_dir}" build -c opt --stamp src:bazel --embed_label ${version}
EOF

cp "${out_dir}/"**"/execroot/io_bazel/bazel-out/k8-opt/bin/src/bazel" "${executable_name}"
shasum -a 256 "${executable_name}" > "${executable_name}.sha256"

./build.sh 5.0.0rc4

Assets 4

16 Dec 00:24

alexeagle

5.0.0rc3

d1dd5cf

5.0 rc3 plus ptarjan fix

Based on the bazelbuild/bazel 5.0.0rc3 branch
https://github.com/bazelbuild/bazel/commits/release-5.0.0rc3

This is released from the aspect-5.0.0rc3 branch in this repo.
Therefore the delta between the upstream Bazel release and ours is
bazelbuild/bazel@release-5.0.0rc3...aspect-build:aspect-5.0.0rc3

We do this because our clients need some fixes and cannot wait for the long journey of getting Google to merge changes and release them.

Built with
bazelbuild/continuous-integration#1290
as the base image -> docker.io/library/bazel:4.2.2

then built using the following script

#!/bin/bash

set -o errexit -o nounset -o pipefail

git_root="$(git rev-parse --show-toplevel)"
out_dir="/tmp/bazel_build_output"
executable_name="bazel-5.0.0rc3-linux-x86_64"

mkdir -p "${out_dir}"

rm -rf "${executable_name}"
rm -rf "${executable_name}.sha256"

docker_args=(
    --volume="${git_root}":/workspace/bazel
    --volume="${out_dir}:${out_dir}"
    --volume=/var/run/docker.sock:/var/run/docker.sock
    --volume="${HOME}/.npm:/home/.npm"
    --workdir=/workspace/bazel
    --publish=3000:3000
)

docker run "${docker_args[@]}" -i --rm --entrypoint=/bin/bash --user=root bazel:4.2.2 <<EOF
apt-get install --yes software-properties-common
add-apt-repository ppa:openjdk-r/ppa
apt-get update
apt-get install --yes openjdk-11-jdk
su ubuntu
bazel --output_user_root="${out_dir}" build -c opt --stamp src:bazel --embed_label 5.0.0rc3
EOF

cp "${out_dir}/"**"/execroot/io_bazel/bazel-out/k8-opt/bin/src/bazel" "${executable_name}"
shasum -a 256 "${executable_name}" > "${executable_name}.sha256"