Google Git
Sign in
gerrit / gerrit / f2c9a3dc7d1017b85770011ed0dc9d05c7b78e84
commitf2c9a3dc7d1017b85770011ed0dc9d05c7b78e84[log] [tgz]
authorDavid Ostrovsky <david@ostrovsky.org>Sat Feb 12 14:53:31 2022 +0100
committerDavid Ostrovsky <david.ostrovsky@gmail.com>Fri Feb 18 18:10:49 2022 +0000
treefd06c8368b2be81e9ac316bb09ebfa27d92015f8
parent547c9e46b9c81fb0192e82dc73d085cfa182cd88 [diff]
Bazel: Bump rules_nodejs version to 5.1.0

See [1] and [2] for some background documentation.

The new dependency on @bazel/concatjs is unfortunate, but that is where
ts_library has moved. And we have spent 2 hours trying to get ts_project
to work instead, and failed. So I guess we have to live with this for
now.

Without `symlink_node_modules` in `yarn_install` the `node_modules`
directory would not appear anymore next to the package.json file. It
would only appear in Bazel's out directories. That breaks all sorts of
things, `server.go` for example cannot cope at all without
`node_modules` being present.

[1] https://github.com/bazelbuild/rules_nodejs/releases/tag/5.0.0
[2] https://github.com/bazelbuild/rules_nodejs/wiki/Migrating-to-5.0

Release-Notes: Update rules_nodejs version to 5.1.0
Change-Id: Iba20c21e9a6ec83fb3c1c2fdd28f2908cdf249cb
11 files changed
tree: fd06c8368b2be81e9ac316bb09ebfa27d92015f8
  1. .settings/
  2. .ts-out/
  3. antlr3/
  4. contrib/
  5. Documentation/
  6. e2e-tests/
  7. java/
  8. javatests/
  9. lib/
  10. modules/
  11. plugins/
  12. polygerrit-ui/
  13. prolog/
  14. prologtests/
  15. proto/
  16. resources/
  17. tools/
  18. webapp/
  19. polymer-bridges
  20. .bazelignore
  21. .bazelproject
  22. .bazelrc
  23. .bazelversion
  24. .editorconfig
  25. .git-blame-ignore-revs
  26. .gitignore
  27. .gitmodules
  28. .gitreview
  29. .mailmap
  30. .pydevproject
  31. .zuul.yaml
  32. BUILD
  33. COPYING
  34. INSTALL
  35. Jenkinsfile
  36. package.json
  37. README.md
  38. SUBMITTING_PATCHES
  39. version.bzl
  40. WORKSPACE
  41. yarn.lock
README.md

Gerrit Code Review

Gerrit is a code review and project management tool for Git based projects.

Build Status Maven Central

Objective

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.

Documentation

For information about how to install and use Gerrit, refer to the documentation.

Source

Our canonical Git repository is located on googlesource.com. There is a mirror of the repository on Github.

Reporting bugs

Please report bugs on the issue tracker.

Contribute

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.

Getting in contact

The Developer Mailing list is repo-discuss on Google Groups.

License

Gerrit is provided under the Apache License 2.0.

Build

Install Bazel and run the following:

    git clone --recurse-submodules https://gerrit.googlesource.com/gerrit
    cd gerrit && bazel build release

Install binary packages (Deb/Rpm)

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>]

Use pre-built Gerrit images on Docker

Docker images of Gerrit are available on DockerHub

To run a CentOS 8 based Gerrit image:

    docker run -p 8080:8080 gerritcodereview/gerrit[:version]-centos8

To run a Ubuntu 20.04 based Gerrit image:

    docker run -p 8080:8080 gerritcodereview/gerrit[:version]-ubuntu20

NOTE: release is optional. Last released package of the version is installed if the release number is omitted.