tree 67b90d150aa783edf93aa22200b218d71db66af1
parent 2095becc2b2a112a8823acf8f5ecf4a4f43346a0
author Xin <xingao267@users.noreply.github.com> 1544025840 -0500
committer GitHub <noreply@github.com> 1544025840 -0500
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJcB/bwCRBK7hj4Ov3rIwAAdHIIAGzmA9hauTj2Hl1hRX2iHXCY
 cVlvzFa+63qR0TOgknvAxvoxVr7SAlHG7x9p4u5i0oSif0Q6lfGF7u930ixZd2E3
 acb1JiWA0FkywXw8ANxEmO5XL9Z87tpyo5qwlAM6lJnMsVwMyHMui8yj4UUzoyO6
 QhLJaC046t+oNRDCkVB9e1/bC6GuQoUmsucefO3ytUdK5O7PXcYW+UDx6kuKh94Z
 eX9TiAfexOhFujCh4rNjrkWP7OQE7+2gYCL7jmWRcxFBIX+fFBBsZVKTsBT9xAs2
 58B3/keWKG0q9T1qBI21DYYzYzRpDNC5Af6/m5u0DfPxTX9CULqUfgx6OahZo8Q=
 =ybaa
 -----END PGP SIGNATURE-----
 

Remove referring to repo itself when using own rules. (#257)

This is to avoid creating infinite symlink expansion in the GCB job to
create containers.

The reason why this is happening is because in the our GCB job, we
intentially set the bazel output_base to be the /workspace directory in
order for some file mounting needed by the base-images-docker to work properly.
/workspace is also where the source code of the repo is located on the
GCB. The side effect of that is if we use bazel_toolchains as another
external dependency (by adding @bazel_toolchains prefix in BUILD or
WORKSPACE when loading bazel_toolchains repo's own rules), then an
infinitie symlink expansion would occur:

[start of symlink chain]
/workspace/external/bazel_toolchains
/workspace
[end of symlink chain]

We currently haven't found a way on GCB to avoid setting the output_base
to be /workspace, and still keep the file mounting working. And putting
the source code into /workspace is done by GCB and cannot be changed.