| commit | 0d8d183a3f2c455b723e8ef3b1e487e4363a5ce2 | [log] [tgz] |
|---|---|---|
| author | Luca Milanesio <[email protected]> | Tue Dec 05 00:52:13 2017 +0000 |
| committer | Luca Milanesio <[email protected]> | Tue Feb 27 15:56:25 2018 +0000 |
| tree | 1c65d47793407b6ba35cfb8aa5ead68364e18333 | |
| parent | fc305e2d99ba4f984630b9a55c01d41cda4c13fd [diff] |
Use old-releases for legacy Ubuntu 15.x Docker The old Gerrit docker VMs are based on Ubuntu 15.x that does not keep anymore the packages under the archive site. Move to old-releases.ubuntu.com so that even old images can still be built and we can release the patch-version of Gerrit legacy on Docker. Change-Id: Ie189d0d24677c285129f4f9374072e79876cff83
This project contains the native Gerrit installation packages for the most popular platforms:
fpm subdirectory contains the Makefile to create RPM and DEB packages for a basic Gerrit installation with the following options:
_become_any_accountYou need to have a Linux with the FPM utility installed. Then execute the following steps from the cloned gerrit-installer project workspace:
RPM/DEBS gets created as fpm/out/gerrit-*.(deb|rpm)
FPM Makefile allows to customise the version and URL where Gerrit war gets downloaded. By overriding the VERSION variable it is possible to build any Gerrit version that is published on Google Releases Storage http://gerrit-releases.storage.googleapis.com/.
In order to build the package for Gerrit Ver. 2.9.4:
RPM/DEBS gets created as fpm/out/gerrit-2.9.4.(deb|rpm)
Gerrit 2.11/master branch is not published on Google Releases Storage, but is available on Gerrit Build Server under the permalink: http://ci.gerritforge.com/job/Gerrit-master/lastSuccessfulBuild/artifact/buck-out/gen/gerrit.war
In order to build the package for Gerrit Ver. 2.11/master:
RPM/DEBS gets created as fpm/out/gerrit-2.11.(deb|rpm)
If you wish to publish the RPMs to a custom or public YUM repo server, you need to sign the packages and create the associated yum.repo definition to be installed on the clients.
The yum-repo directory contains a Makefile that is designed to help you in automating the repo creation and client configuration.
In order to build a YUM repository you need to have already generated the RPMs as indicated in the previous steps and then execute:
A client RPM package will be generated under the client sub-directory and will need to be installed manually on the clients in order to configure your YUM repository.
A YUM repo structure will be generated under the server sub-directory and will need to be uploaded to your HTTP Web-Server or to a public repository service (e.g. BinTray or even GitHub).
NOTE: By default the yum-repo generated will use the GerritForge credentials. Should you need to publish your own repository you would need to generate your own PGP private/public keys and override the vendor's definitions.
In order to generate a customized vendor's settings for the yum-repo, you need to execute:
NOTE: The yum-repo settings are assuming that you are publishing the yum-repo server and make the URL listed on http://mirrorlist.mycompany.com/yum