Merge pull request kocolosk#2 from natarajaya/master

[GPII-3624]: Makefile, GitLab config, updated README

Author: natarajaya

.gitlab-ci.yml

@@ -0,0 +1,19 @@
+stages:
+  - build
+
+build-push-master:
+  stage: build
+  script:
+    - make build
+    - make push
+  only:
+    refs:
+      - master
+
+build-push-tag:
+  stage: build
+  script:
+    - make build-tag
+    - make push-tag
+  only:
+    - tags

Makefile

@@ -0,0 +1,22 @@
+.PHONY: help build build-tag push
+.DEFAULT_GOAL:= help
+.ONESHELL:
+
+DOCKER_IMAGE = gpii/couchdb-statefulset-assembler
+
+help:                     ## Prints list of tasks
+	@awk 'BEGIN {FS = ":.*?## "} /^[a-zA-Z0-9_-]+:.*?## / {printf "\033[36m%-30s\033[0m %s\n", $$1, $$2}' Makefile
+
+build:                    ## Build image as latest
+	docker build -t "${DOCKER_IMAGE}:latest" ./
+
+build-tag:                ## Build image as tag (use CI_COMMIT_TAG env var)
+	@CI_COMMIT_TAG="$${CI_COMMIT_TAG:?Required variable not set}"
+	docker build -t "${DOCKER_IMAGE}:${CI_COMMIT_TAG}" ./
+
+push:                     ## Push image - latest
+	docker push "${DOCKER_IMAGE}:latest"
+
+push-tag:                 ## Push image - tag
+	@CI_COMMIT_TAG="$${CI_COMMIT_TAG:?Required variable not set}"
+	docker push "${DOCKER_IMAGE}:${CI_COMMIT_TAG}"

README.md

@@ -11,3 +11,33 @@ cluster is automically joined up.
 If the deployment is scaled *up* after the initial creation those new Pods will
 be automatically added. Scaling *down* does not automatically remove the Pods
 from the membership database at this time.
+
+## Building
+
+### Master
+
+On push/merge to master, CI will automatically build and push
+`gpii/couchdb-statefulset-assembler:latest` image.
+
+### Tags
+
+Create and push git tag and CI will build and publish corresponding `gpii/couchdb-statefulset-assembler:${git_tag}` docker image.
+
+#### Tag format
+
+Tags should follow actual couchdb-statefulset-assembler version, suffixed by
+`-gpii.${gpii_build_number}`, where `gpii_build_number` is monotonically
+increasing number denoting Docker image build number,  starting from `0`
+for each upstream version.
+
+Example:
+```
+0.0.3-gpii.0
+0.0.3-gpii.1
+...
+0.0.4-gpii.0
+```
+
+### Manually
+
+Run `make` to see all available steps.