| commit | d35e0b324c876fe0a24e4c817d0245815721f953 | [log] [tgz] |
|---|---|---|
| author | Yu Yi <yiyu@google.com> | Wed Dec 06 10:26:44 2017 -0500 |
| committer | Yu Yi <yiyu@google.com> | Wed Dec 06 16:08:59 2017 +0000 |
| tree | b9499b9ccb88a468666eb21855069d115ee9353f | |
| parent | 632bc3fd9b97e4cf6c5e802279c0a614c5850c6d [diff] |
create py.tar.gz which omits timestamps
* By doing this, we will get the same py.tar.gz everytime, so that we
will have reproducible fully-loaded container with a same sha256
Tested:
- started two builds and ends with docker images with a same sha256
- container/debian8-clang-fully-loaded/build.sh -p my-project -c
debian8-clang-fl -t test-image-{1,2} -a
Change-Id: Ib8bb050b7e050f879709742dfff4ac9f8960975b
EDIT
https://github.com/bazelbuild/bazel-toolchains is a repository where Google hosts Bazel toolchain configs. These configs are required to configure Bazel to issue commands that will execute inside a Docker container via a remote execution environment.
These toolchain configs include:
Release information of toolchain configs can be found at: https://releases.bazel.build/bazel-toolchains.html.
This repository also hosts the skylark rule used to generate toolchain configs.