github.com/sl1pm4t/terraform@v0.6.4-0.20170725213156-870617d22df3/scripts/docker-release/README.md (about)

     1  # Terraform Docker Release Build
     2  
     3  This directory contains configuration to drive the Dockerhub automated build
     4  for Terraform. This is different than the root Dockerfile (which produces
     5  the "full" image on Dockerhub) because it uses the release archives from
     6  releases.hashicorp.com. It is therefore not possible to use this configuration
     7  to build an image for a commit that hasn't been released.
     8  
     9  ## How it works
    10  
    11  Dockerhub runs the `hooks/build` script to trigger the build. That uses
    12  `git describe` to identify the tag corresponding to the current `HEAD`. If
    13  the current commit _isn't_ tagged with a version number corresponding to
    14  a Terraform release already on releases.hashicorp.com, the build will fail.
    15  
    16  ## What it produces
    17  
    18  This configuration is used to produce the "latest", "light", and "beta"
    19  tags in Dockerhub, as well as specific version tags.
    20  
    21  * "latest" and "light" are synonyms, and are built from a branch in this
    22  repository called "stable".
    23  * "beta" is built from a branch called "beta".
    24  
    25  All of these branches should be updated only to _tagged_ commits, and only when
    26  it is desirable to create a new release image.
    27  
    28  ## The `full` and `master` images image
    29  
    30  This configuration does not produce the "full" image. That is instead produced
    31  by the `Dockerfile` in the repository root, driven by updates to the "stable"
    32  branch.
    33  
    34  The "master" tag is updated for _every_ commit to the master branch of
    35  the Terraform core repository. It is not recommended to use these images for
    36  any production use, but they can be useful for testing bleeding-edge features
    37  that are not yet included in a release.