Release candidate M2

Ongoing work for #73

• Terraform 0.12 branch synced with develop branch (tf 0.11).
• Added fix for docs generation

Release candidate M1

First milestone release for conversion of the module to Terraform 0.12

Release 3.6.0

• Changed
  • Add option to specify pull policy for docker images by the runner. @roock
  • Docker machine AMI image will be by default latest ubuntu 16.06, can be overwritten via variables @roock
  • Improved CI docs generation script @roock

Release 3.5.0

• Changed
  • Documentation #85: Misleading Variable-Description @solutionDrive-Alt
  • Bugfix #70: docker-machine fails starting runners when amazonec2-request-spot-instance=false @philippefuentes
  • Bugfix #72: Detect and retry when docker machine installation fails @eliasdorneles
  • Changed: Default version of GitLab runner set to 11.11.2

3.4.0

• Changed:
  • Update default runner type, GitLab runner version, and versions in examples.
  • Buffix #75 runner is not reachable when runners_use_private_address = false @int128
  • Buffix - Missing typ - @Orkin
  • Bugfix #72 - Detect and retry when docker machine download fails e@liasdorneles
  • Bugfix #68 - add count to prevent resource creation failing @philippefuentes
  • Bugfix #70 - update policy to allow runners to start when not using spot instances @philippefuentes

Release 3.3.0

• Changed: Default version of GitLab runner set to 11.10.1
• Added: Option to enable / disable SSH login
• Added: Option to use spot instances for runner instance
• Changed: Default instance type is now m5.large
• Added: Custom names for instance and security groups

Thanks to @mpas @@userhas404d @@allanlegalstart @arrpee

Release 3.2.0

Added: Option to set shm_size for the runners, default remains 0. thanks to @BMonsalvatge

Release 3.1.0

• Added: Option to set environment variables for the runners, see the variable runners_environment_vars. An example added to the public-runner example. Thanks to @reach3r

Release 3.0.0

As of this release the runner will be registered automatically by providing the registration token. The previous way of registering the runner via the the runners_token is still supported. Thanks to @PatrickWolleb and @JeroenKnoops

Migration directions

The variable runners_token will become obsolete and replace it by a runner configuration which will be used to register the runner.

Define in the module the runner configuration as follow:

  gitlab_runner_registration_config = {
    registration_token = "<registration token>"
    tag_list           = "<your tags, comma separated"
    description        = "<some description>"
    locked_to_project  = "true"
    run_untagged       = "false"
    maximum_timeout    = "3600"
  }

And DO NOT specify the runners_token. The runner will then be created if there is not one registered before. Registered runners will be stored in the AWS parameter store.

For migration to the new setup simply add the runner token to the parameter store. Once the runner is started it will lookup required values in the parameter store. If the value is null a new runner will be created.

# set the following variables, look up the variables in your Terraform config.
# see your Terraform variables to fill in the vars below.
aws-region=<${var.aws_region}>
token=<runner-token-see-your-gitlab-runner>
parameter-name=<${var.environment}>-<${var.secure_parameter_store_runner_token_key}>

aws ssm put-parameter --overwrite --type SecureString  --name "${parameter-name}" --value ${token} --region "${aws-region}"

Once you have created the parameter, you have to remove the variable runners_token from your config. Then next time your gitlab runner instance is created it look up the token from the parameter store.

See also the README and examples for more details.

Release 2.3.0

• Bugfix: Added a profile for the docker machine runners. #41 thanks to @msvechla
• Changed: Changed the name of runner instance, added docker-machine to the name.