Releases: cattle-ops/terraform-aws-gitlab-runner
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
Release 2.2.1
- Bugfix: Add tags to spot instances #39
- Changed: Updated terraform providers in examples and default terraform version
Release 2.2.0
- Changed: Upgrade default runner agent to 11.8.0 and docker machine to 0.16.1
- Bugfix: Correct example for docker_machine_options #36 (@declension)
- Added: AWS Zone variable #35 (@declension)
Release 2.1.0
Release 2.0.0
- Changed: Replaced cache user by a instance profile to access the cache from the build
- Changed: Update gitlab toml cache section, removed deprecated usages of s3
- Changed: The variable
amazon_optimized_amis
is removed an replaced by a filter to select the AMI. To use the default of the latest AMI set the filterami_filter
toamzn-ami-hvm-2018.03.0.20180622-x86_64-ebs
. - Added: Option to set docker machine options via
docker_machine_optionns
. - Added: Several output variables.
Release 1.8.0
Changelog
- Changed: Updated default docker-machine version to 0.16.0
- Changed: Updated default gitlab runner to 11.6.0
- Added: Configuration parameters for post_build_script, pre_clone_script, request_concurrency and output_limit. #22
- Added: Configurable docker image for runner #27
- Added: Add pre/post install user-data snippets for runners #26
Contributions
Release 1.5.0
Updated default AMI map to Amazon Linux AMI 2018.03 was released on 2018-06-28
Release 1.4.0
[1.4.0] - 2018-08-09
Added
- Added an option to allow gitlab runner instance to create service linked roles, by default enabled.
- Added example for public subnet
Release 1.3.0
Release 1.3.0