Repository files navigation

This role will install theofficial GitLab Runner(fork from haroldb) with updates. Needed something simple and working, this did the trick for me. Open for changes though.

This role requires:

• Ansible 2.13 or higher
• Installed Ansible Galaxy collections listed in filerequirements.yml

• gitlab_runner_package_name -As of GitLab 10.x, the package namegitlab-ci-multi-runner has been renamed togitlab-runner. To install a version earlier than 10.x, define the variablegitlab_runner_package_name: gitlab-ci-multi-runner.
• gitlab_runner_wanted_version orgitlab_runner_package_version - Use these to install a specific version of the GitLab Runner (by default, the latest version is installed).
  • On macOS and Windows, usegitlab_runner_wanted_version: 12.4.1 (example).
  • On Linux, usegitlab_runner_package_version instead.
• gitlab_runner_concurrent - Defines the maximum number of jobs that can run concurrently. Defaults to the number of processor cores.
• gitlab_runner_registration_token - The GitLab registration token. If specified, this will register each runner with a GitLab server.Note: This token can only be used globally ifgitlab_runner_registration_token_type is set to the deprecatedregistration-token. Otherwise, you must specify atoken for each item ingitlab_runner_runners, as shown in the example playbook below. This token is deprecated in GitLab version 16.0 and will be removed in version 18.0.
• gitlab_runner_registration_token_type - Specifies the type of registration token to use for GitLab Runner registration:
  • Set to "authentication-token" to register the runner with the--token option (following the new workflow:https://docs.gitlab.com/ee/ci/runners/new_creation_workflow.html).
  • Set to "registration-token" to register the runner with the--registration-token option. This is deprecated in GitLab 16.0 but remains usable until it is removed in version 18.0.
  • For GitLab version 16.0 and above, it is recommended to specify a token for each runner in thegitlab_runner_runners section and set this variable to "authentication-token".
• gitlab_runner_coordinator_url - The GitLab coordinator URL. Defaults tohttps://gitlab.com.
• gitlab_runner_sentry_dsn - Enables tracking of system-level errors to Sentry.
• gitlab_runner_listen_address - Enables the/metrics endpoint for Prometheus scraping.
• gitlab_runner_runners - A list of GitLab runners to register and configure. By default, this is set to a single shell executor.
• gitlab_runner_skip_package_repo_install - Skips the installation of the APT or YUM repository (default: false). You should ensure that the necessary packages are available in your repository before running this role.
• gitlab_runner_config_update_mode - Defines how configuration updates are applied:
  • Set toby_config_toml (default) to apply configuration changes directly by updating theconfig.toml file.
  • Set toby_registering if changes should be applied by unregistering and re-registering the runner when configuration changes.
  • Set toby_template if changes for all runners should directly be written in theconfig.toml file. The difference withby_config_toml is that this method is faster, but does not take into account the existing configuration of the runners. You may also have to provide additional configuration options for each runner, such asid andtoken_obtained_at.
• gitlab_unregister_runner_executors_which_are_not_longer_configured - Set totrue if executors should be unregistered from a runner when they are no longer configured in Ansible. Default:false.

See thedefaults/main.yml file for a list of all possible options that can be passed to a runner registration command.

For each gitlab runner in gitlab_runner_runners you can set cache options. At the moment role support s3, azure and gcs types.Example configurration for s3 can be:

gitlab_runner:cache_type:"s3"cache_path:"cache"cache_shared:truecache_s3_server_address:"s3.amazonaws.com"cache_s3_access_key:"<access_key>"cache_s3_secret_key:"<secret_key>"cache_s3_bucket_name:"<bucket_name>"cache_s3_bucket_location:"eu-west-1"cache_s3_insecure:false

• MachineOptions: [] - Foremost you need to pass an array of dedicated vars in the machine_options to configure your scaling runner:

  • amazonec2-access-key andamazonec2-secret-key the keys of the dedicated IAM user with permission for EC2
  • amazonec2-zone
  • amazonec2-region
  • amazonec2-vpc-id
  • amazonec2-subnet-id
  • amazonec2-use-private-address=true
  • amazonec2-security-group
  • amazonec2-instance-type
  • you can also setamazonec2-tags to identify you instance more easily via aws-cli or the console.

• MachineDriver - which should be set toamzonec2 when working on AWS

• MachineName - Name of the machine. Itmust contain%s, which will be replaced with a unique machine identifier.

• IdleCount - Number of machines, that need to be created and waiting in Idle state.

• IdleTime - Time (in seconds) for machine to be in Idle state before it is removed.

• MaxGrowthRate - The maximum number of machines that can be added to the runner in parallel. Default is 0 (no limit).

• MaxBuilds - Maximum job (build) count before machine is removed.

• IdleScaleFactor - (Experimental) The number of Idle machines as a factor of the number of machines currently in use. Must be in float number format. See the autoscale documentation for more details. Defaults to 0.0.

• IdleCountMin - Minimal number of machines that need to be created and waiting in Idle state when the IdleScaleFactor is in use. Default is 1.

For details follow these links:

• gitlab-docs/runner: advanced configuration: runners.machine section
• gitlab-docs/runner: autoscale: supported cloud-providers
• gitlab-docs/runner: autoscale_aws: runners.machine section

See theconfig for more options

-hosts:allbecome:truevars_files:    -vars/main.ymlroles:    -{ role: riemers.gitlab-runner }

Insidevars/main.yml

gitlab_runner_coordinator_url:https://gitlab.comgitlab_runner_registration_token:'12341234'gitlab_runner_runners:  -name:'Example Docker GitLab Runner'# token is an optional override to the global gitlab_runner_registration_tokentoken:'abcd'# url is an optional override to the global gitlab_runner_coordinator_urlurl:'https://my-own-gitlab.mydomain.com'executor:dockerdocker_image:'alpine'tags:      -node      -ruby      -mysqldocker_volumes:      -"/var/run/docker.sock:/var/run/docker.sock"      -"/cache"extra_configs:runners.docker:memory:512mallowed_images:["ruby:*", "python:*", "php:*"]runners.docker.sysctls:net.ipv4.ip_forward:"1"

howvars/main.yml would look like, if you setup an autoscaling GitLab-Runner on AWS:

gitlab_runner_registration_token:'HUzTMgnxk17YV8Rj8ucQ'gitlab_runner_coordinator_url:'https://gitlab.com'gitlab_runner_runners:  -name:'Example autoscaling GitLab Runner'state:present# token is an optional override to the global gitlab_runner_registration_tokentoken:'HUzTMgnxk17YV8Rj8ucQ'executor:'docker+machine'# Maximum number of jobs to run concurrently on this specific runner.# Defaults to 0, simply means don't limit.concurrent_specific:'0'docker_image:'alpine'# Indicates whether this runner can pick jobs without tags.run_untagged:truemachine_IdleCount:1machine_IdleTime:1800machine_MaxBuilds:10machine_MachineDriver:'amazonec2'machine_MachineName:'git-runner-%s'machine_MachineOptions:["amazonec2-access-key={{ lookup('env','AWS_IAM_ACCESS_KEY') }}", "amazonec2-secret-key={{ lookup('env','AWS_IAM_SECRET_KEY') }}", "amazonec2-zone={{ lookup('env','AWS_EC2_ZONE') }}", "amazonec2-region={{ lookup('env','AWS_EC2_REGION') }}", "amazonec2-vpc-id={{ lookup('env','AWS_VPC_ID') }}", "amazonec2-subnet-id={{ lookup('env','AWS_SUBNET_ID') }}", "amazonec2-use-private-address=true", "amazonec2-tags=gitlab-runner", "amazonec2-security-group={{ lookup('env','AWS_EC2_SECURITY_GROUP') }}", "amazonec2-instance-type={{ lookup('env','AWS_EC2_INSTANCE_TYPE') }}"]machine_autoscaling:      -Periods:["* * 7-18 * * mon-fri *"]Timezone:"UTC"IdleCount:3IdleTime:900      -Periods:["* * * * * sat,sun *"]Timezone:"UTC"IdleCount:0IdleTime:300

fromhttps://docs.gitlab.com/runner/executors/docker_machine.html:

Thefirst time you’re using Docker Machine, it’s best to executemanuallydocker-machine create... with your chosen driver andall options from the MachineOptions section. This will set up the Docker Machine environment properly and will also be a good validation of the specified options. After this, youcan destroy the machine withdocker-machine rm [machine_name] and start the Runner.

Example:

docker-machine rm test

To run the Gitlab Runner as a different user (rather than the defaultgitlab-runner user), there is a workaround requiring a littleextra Ansible to be run. Seeriemers#277 for details.

Feel free to add your name to the readme if you make a PR. A full list of people from the PR's ishere

• Gastrofix for adding Mac Support
• Matthias Schmieder for adding Windows Support
• dniwdeus & rosenstrauch for adding AWS autoscale option
• oscillate123 for fixing Windows config.toml idempotency
• cchaudier for fixing changing the version of a package which is on the apt hold list