Get SHA1 of the local config to tag Gerrit image

The Gerrit image depends not only on the data that is
stored on the templates but also from the values set
in the *.setup files in the image directory.

Include a SHA1 of all the content of the files used
for building the Gerrit image so that it won't clash
with other configuration settings used by other users
based on the same templates.

E.g. User John and Matt using the same commit of
the aws-gerrit repo but with different *.setup files would
result in different images tags, avoiding clashing between
each other.

Change-Id: Idcbee1c89fd6855321f2cdfa7293611a925c368c
1 file changed
tree: 5ad452c4a692a1797b59256cbb241c27c67c528b
  1. dual-master/
  2. gerrit/
  3. ldap/
  4. master-slave/
  5. monitoring/
  6. single-master/
  7. .gitignore
  8. common.env
  9. LICENSE
  10. Makefile.common
  11. README.md
README.md

Gerrit AWS Templates

Those are a collection of AWS CloudFormation templates and scripts to deploy Gerrit in AWS.

The aim is to provide some guidelines and example on how to deploy different Gerrit setups in the Cloud using AWS as provider.

Outline

Overview

The goal of Gerrit AWS Templates is to provide fully-functional Gerrit installations to helps users deploying Gerrit on AWS by providing out-of-the-box templates.

With Gerrit AWS Templates, developers and administrator can create a production-ready installation on the cloud in minutes and in a repeatable way, allowing them to focus on fine tuning of the Gerrit configuration to suit the user needs.

The provided CloudFormation templates automate the entire creation and deployment of the infrastructure and the application.

Pre-requisites

To manage your AWS services via command line you will need to install AWS CLI and set it up to point to your account.

Templates