| commit | ac56c313df61dc1fc7667b41d9fb04eb34224c8e | [log] [tgz] |
|---|---|---|
| author | Dave Borowitz <dborowitz@google.com> | Mon Apr 16 12:05:38 2018 +0200 |
| committer | Dave Borowitz <dborowitz@google.com> | Mon Apr 16 12:05:39 2018 +0200 |
| tree | 45b88e1597efcf60bdf3b398d8644311bcb6c730 | |
| parent | d620ad1043f86104dfc2a0059c233fac34c36efa [diff] |
bazel: Recommend setting --action_env=PATH for local cache
The old configuration makes it impossible to compile Gerrit on Mac with
recent versions of Bazel. The flag --experimental_strict_action_env now
makes Bazel pass PATH=/bin:/usr/bin to subcommands. Building PolyGerrit
requires using node from $PATH. On Macs it is impossible (even for root)
to write to /usr/bin, so node has to live somewhere not in that
hard-coded PATH. I'm not sure when this behavior changed in Bazel; it
seems like it should have broken long ago. But it's marked experimental
so we can't complain too much.
The documentation of this option says:
If true, Bazel uses an environment with a static value for PATH and does
not inherit LD_LIBRARY_PATH or TMPDIR. Use --action_env=ENV_VARIABLE if you
want to inherit specific environment variables from the client, but note
that doing so can prevent cross-user caching if a shared cache is used.
Passing --action_env=PATH fixes the problem. I think it should be
safe(ish) to pass --action_env=PATH, since the particular setup
described in our docs is not used for cross-user caching. This may not
catch potential cache invalidations due to different versions of tools,
but I don't see how it's any worse than when the binaries in /usr/bin
get updated.
Change-Id: I94543bd4801b83a66ff150baf3fb9e12ded7555f
Gerrit is a code review and project management tool for Git based projects.
Gerrit makes reviews easier by showing changes in a side-by-side display, and allowing inline comments to be added by any reviewer.
Gerrit simplifies Git based project maintainership by permitting any authorized user to submit changes to the master Git repository, rather than requiring all approved changes to be merged in by hand by the project maintainer.
For information about how to install and use Gerrit, refer to the documentation.
Our canonical Git repository is located on googlesource.com. There is a mirror of the repository on Github.
Please report bugs on the issue tracker.
Gerrit is the work of hundreds of contributors. We appreciate your help!
Please read the contribution guidelines.
Note that we do not accept Pull Requests via the Github mirror.
The IRC channel on freenode is #gerrit. An archive is available at: echelog.com.
The Developer Mailing list is repo-discuss on Google Groups.
Gerrit is provided under the Apache License 2.0.
Install Bazel and run the following:
git clone --recursive https://gerrit.googlesource.com/gerrit
cd gerrit && bazel build release
The instruction how to configure GerritForge/BinTray repositories is here
On Debian/Ubuntu run:
apt-get update & apt-get install gerrit=<version>-<release>
NOTE: release is a counter that starts with 1 and indicates the number of packages that have been released with the same version of the software.
On CentOS/RedHat run:
yum clean all && yum install gerrit-<version>[-<release>]
On Fedora run:
dnf clean all && dnf install gerrit-<version>[-<release>]
Docker images of Gerrit are available on DockerHub
To run a CentOS 7 based Gerrit image:
docker run -p 8080:8080 gerritforge/gerrit-centos7[:version]
To run a Ubuntu 15.04 based Gerrit image:
docker run -p 8080:8080 gerritforge/gerrit-ubuntu15.04[:version]
NOTE: release is optional. Last released package of the version is installed if the release number is omitted.