[Announce] Gerrit 2.10 - Native packages distributions available

lucamilanesio

unread,

Feb 26, 2015, 3:00:43 PM2/26/15

to repo-d...@googlegroups.com

Hi all,

I am pleased to announce the general availability of RPM, Deb native distributions for Gerrit 2.10.

They are packaged from the original Gerrit WAR previously released, using the new native installers tools developed for Gerrit [1].

Why another yet another packaging?

Many companies use the Linux native software packaging tool to standardise the way they install and update software.

Additionally it is easier to trace tools compatibility matrix and dependencies and update them accordingly.

Last but not least allows to be always updated to the latest patch-level on existing installations.

What type of packages are provided?

We started by providing:

- RPM packages for RedHat / CentOS

- Deb packages for Debian / Ubuntu

That is really cool ! How can I get the Gerrit packages?

Gerrit packages are distributed using the native repository distribution system provided by the Linux distribution.

On CentOS / RedHat you need to define one extra YUM repository pointing to the Gerrit distribution site.

To facilitate the set-up, GerritForge provided an RPM that will do the job, to install it just execute:

rpm -i https://gerritforge.com/gerritforge-repo-1-1.noarch.rpm

Once the YUM repo is installed, you can simply execute:

yum install -y gerrit

On Ubuntu / Debian you need to define the extra source pointing to the Gerrit distribution site:

echo "deb mirror://mirrorlist.$(VENDOR_LC).com/deb gerrit contrib" > /etc/apt/sources.list.d/gerritforge.list

and then download the PGP signing key and update the repository list

apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 1871F775
apt-get update

Once the Debian source is defined you can simply execute:
apt-get install gerrit

Hold on, isn't that even more complex than just running Gerrit init wizard?

Yes and no. For the first repository set-up the answer is yes, it is more complex because of the set-up of a YUM or Debian repository.

Once the repository set-up phase is finalised, then installing a working version of gerrit is just one command away.

Additional once configured for production, the configuration files are kept across updates and you can get constantly aligned with the most updated patch-level for your installation.

Who is hosting Gerrit native packages?

We would like to thank JFrog and GerritForge for having provided their download sites for hosting the native packages. The list of sources can be extended as the native packaging systems allow to define a set of mirrors that are automatically selected based on your location and speed.

If anyone is willing to host a mirror of those native packages, please contact me and we'll update the official list of mirrors available.

Can I customise the Gerrit native packages and make a tailored version for my Company?

Yes, the native packages are built using 100% OpenSource tools and scripts published on [1]. Just checkout the gerrit-installer project and make the packages again defining your desired version, organisation and distribution URLs.

What's next?

We are going to publish soon more native packaging formats:

Docker (coming veeeery soon)
MacOS Pkg
Windows MSI

References

[1] https://gerrit-review.googlesource.com/#/admin/projects/gerrit-installer

Luca Milanesio

unread,

Feb 26, 2015, 5:41:25 PM2/26/15

to repo-d...@googlegroups.com

ERRATA-CORRIGE on the Ubuntu / Debian distribution site, see below …

On 26 Feb 2015, at 20:00, lucamilanesio <luca.mi...@gmail.com> wrote:

Hi all,
I am pleased to announce the general availability of RPM, Deb native distributions for Gerrit 2.10.
They are packaged from the original Gerrit WAR previously released, using the new native installers tools developed for Gerrit [1].

Why another yet another packaging?

Many companies use the Linux native software packaging tool to standardise the way they install and update software.
Additionally it is easier to trace tools compatibility matrix and dependencies and update them accordingly.
Last but not least allows to be always updated to the latest patch-level on existing installations.

What type of packages are provided?

We started by providing:
- RPM packages for RedHat / CentOS
- Deb packages for Debian / Ubuntu

That is really cool ! How can I get the Gerrit packages?

Gerrit packages are distributed using the native repository distribution system provided by the Linux distribution.

On CentOS / RedHat you need to define one extra YUM repository pointing to the Gerrit distribution site.
To facilitate the set-up, GerritForge provided an RPM that will do the job, to install it just execute:
rpm -i https://gerritforge.com/gerritforge-repo-1-1.noarch.rpm

Once the YUM repo is installed, you can simply execute:
yum install -y gerrit

On Ubuntu / Debian you need to define the extra source pointing to the Gerrit distribution site:
echo "deb mirror://mirrorlist.$(VENDOR_LC).com/deb gerrit contrib" > /etc/apt/sources.list.d/gerritforge.list

The correct source definition command line is:

echo "deb mirror://mirrorlist.gerritforge.com/deb gerrit contrib" > /etc/apt/sources.list.d/gerritforge.list

and then download the PGP signing key and update the repository list
apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 1871F775
apt-get update
Once the Debian source is defined you can simply execute:
apt-get install gerrit
Hold on, isn't that even more complex than just running Gerrit init wizard?
Yes and no. For the first repository set-up the answer is yes, it is more complex because of the set-up of a YUM or Debian repository.
Once the repository set-up phase is finalised, then installing a working version of gerrit is just one command away.
Additional once configured for production, the configuration files are kept across updates and you can get constantly aligned with the most updated patch-level for your installation.
Who is hosting Gerrit native packages?
We would like to thank JFrog and GerritForge for having provided their download sites for hosting the native packages. The list of sources can be extended as the native packaging systems allow to define a set of mirrors that are automatically selected based on your location and speed.
If anyone is willing to host a mirror of those native packages, please contact me and we'll update the official list of mirrors available.
Can I customise the Gerrit native packages and make a tailored version for my Company?
Yes, the native packages are built using 100% OpenSource tools and scripts published on [1]. Just checkout the gerrit-installer project and make the packages again defining your desired version, organisation and distribution URLs.
What's next?
We are going to publish soon more native packaging formats:

Docker (coming veeeery soon)
MacOS Pkg
Windows MSI
References
[1] https://gerrit-review.googlesource.com/#/admin/projects/gerrit-installer

--
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en

---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Fabio Porcedda

unread,

Mar 2, 2015, 6:28:50 AM3/2/15

to repo-d...@googlegroups.com

On Thursday, February 26, 2015 at 9:00:43 PM UTC+1, lucamilanesio wrote:

Hi all,
I am pleased to announce the general availability of RPM, Deb native distributions for Gerrit 2.10.
They are packaged from the original Gerrit WAR previously released, using the new native installers tools developed for Gerrit [1].

Thanks.

<snip>

Hold on, isn't that even more complex than just running Gerrit init wizard?
Yes and no. For the first repository set-up the answer is yes, it is more complex because of the set-up of a YUM or Debian repository.
Once the repository set-up phase is finalised, then installing a working version of gerrit is just one command away.
Additional once configured for production, the configuration files are kept across updates and you can get constantly aligned with the most updated patch-level for your installation.

About the update process using these packages, what is the correct procedure?

1) Just a "yum update" and the server is restarted and a "java -jar gerrit.war init -d site_path" is done automatically

2) we must stop it, issue a "java -jar gerrit.war init -d site_path" and the end start it again?

Best regards

Fabio Porcedda

unread,

Mar 2, 2015, 11:01:08 AM3/2/15

to Luca Milanesio, Repo and Gerrit Discussion

On Mon, Mar 2, 2015 at 4:25 PM, Luca Milanesio <luca.mi...@gmail.com> wrote:
> Hi Fabio,
> yum update will do the job, the post-update script would stop Gerrit and
> exec the install & reindex.

That's great.

> Luca
>
> Sent from my iPhone

> --
> --
> To unsubscribe, email repo-discuss...@googlegroups.com
> More info at http://groups.google.com/group/repo-discuss?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Repo and Gerrit Discussion" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to repo-discuss...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

--
Fabio Porcedda

Reply all

Reply to author

Forward