5c8ff928ba
#15596 set things up with the intent that the docker image build process would be handled by the automated build system on dockerhub, but after merging we found that it's impossible to change the source git repository for an existing dockerhub repository. To get away from the limitations of dockerhub, we intend to eventually automate these builds in a separate CI system. Here we add some scripts that would drive such an automated process. It's split into multiple steps to allow for situations where the new version should not be tagged as the latest, and to make it easier and safer to test the build script while doing development on it. Since this automated process doesn't yet exist, a wrapper script release.sh is included to help run a local, manual build and deploy process in the mean time. The README.md in the docker-release dir here contains details on the intended usage.
2.9 KiB
Terraform Docker Release Build
This directory contains configuration to drive the docker image releases for Terraform.
Two different types of image are produced for each Terraform release:
-
A "light" image that includes just the release binary that should match what's on releases.hashicorp.com.
-
A "full" image that contains all of the Terraform source code and a binary built from that source.
The latter can be produced for any arbitrary commit by running docker build
in the root of this repository. The former requires that the release archive
already be deployed on releases.hashicorp.com.
Build and Release
The scripts in this directory are intended for running the steps to build,
tag, and push the two images for a tagged and released version of Terraform.
They expect to be run with git HEAD pointed at a release tag, whose name
is used to determine the version to build. The version number indicated
by the tag that HEAD is pointed at will be referred to below as
the current version.
-
build.shbuilds locally both of the images for the current version. This operates on the local docker daemon only, and produces tags that include the current version number. -
tag.shupdates thelatest,lightandfulltags to refer to the images for the current version, which must've been already produced by an earlier run ofbuild.sh. This operates on the local docker daemon only. -
push.shpushes the current version tag and thelatest,lightandfulltags up to dockerhub for public consumption. This writes images to dockerhub, and so it requires docker credentials that have access to write into thehashicorp/terraformrepository.
Releasing a new "latest" version
In the common case where a release is going to be considered the new latest
stable version of Terraform, the helper script release.sh orchestrates
all of the necessary steps to release to dockerhub:
$ git checkout v0.10.0
$ scripts/docker-release/release.sh
Behind the scenes this script is running build.sh, tag.sh and push.sh
as described above, with some extra confirmation steps to verify the
correctness of the build.
This script is interactive and so isn't suitable for running in automation. For automation, run the individual scripts directly.
Releasing a beta version or a patch to an earlier minor release
The release.sh wrapper is not appropriate in two less common situations:
-
The version being released is a beta or other pre-release version, with a version number like
v0.10.0-beta1orv0.10.0-rc1. -
The version being released belongs to a non-current minor release. For example, if the current stable version is
v0.10.1but the version being released isv0.9.14.
In both of these cases, only the specific version tag should be updated, which can be done as follows:
$ git checkout v0.11.0-beta1
$ scripts/docker-release/build.sh
$ docker push hashicorp/terraform:0.11.0-beta1