The version numbers of the helm charts are managed automatically with a script:
|
version: 0.17.1 # managed version |
However, the versions of all the dependencies across the Dockerfiles, docker-compose .env files, and helm charts, are not managed automatically and must be updated manually before a gaffer-docker release:
|
ARG BASE_IMAGE_NAME=gchq/accumulo |
|
ARG BASE_IMAGE_TAG=1.9.3 |
|
|
|
FROM ${BUILDER_IMAGE_NAME}:${BUILDER_IMAGE_TAG} as builder |
|
|
|
ARG GAFFER_VERSION=1.21.1 |
|
ARG GAFFER_LIBS=bitmap-library,sketches-library,time-library |
|
GAFFER_VERSION=1.21.1 |
|
GAFFER_TOOLS_VERSION=1.21.1 |
|
ACCUMULO_VERSION=1.9.3 |
|
HADOOP_VERSION=3.2.1 |
|
image: |
|
repository: gchq/gaffer-rest |
|
tag: 1.21.1 |
Not only is this tedious for releases, requiring manual update commits, but it is also error-prone as this manual process could be done wrong, or different versions could be inconsistent with each other.
Therefore, a way of managing these versions should be added so it can be done automatically at time of release, and safely.
The version numbers of the helm charts are managed automatically with a script:
gaffer-docker/kubernetes/gaffer-road-traffic/Chart.yaml
Line 19 in 41f9f51
However, the versions of all the dependencies across the Dockerfiles, docker-compose .env files, and helm charts, are not managed automatically and must be updated manually before a gaffer-docker release:
gaffer-docker/docker/gaffer/Dockerfile
Lines 18 to 24 in 377655a
gaffer-docker/docker/gaffer/.env
Lines 1 to 4 in 377655a
gaffer-docker/kubernetes/gaffer/values.yaml
Lines 56 to 58 in 377655a
Not only is this tedious for releases, requiring manual update commits, but it is also error-prone as this manual process could be done wrong, or different versions could be inconsistent with each other.
Therefore, a way of managing these versions should be added so it can be done automatically at time of release, and safely.