Adoptable Cookbooks List

Looking for a cookbook to adopt? You can now see a list of cookbooks available for adoption!
List of Adoptable Cookbooks

Supermarket Belongs to the Community

Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.

Select Badges

Select Supported Platforms


gitlab-ci-runner (21) Versions 1.2.0

Installs/Configures Gitlab CI Runner

cookbook 'gitlab-ci-runner', '= 1.2.0'
cookbook 'gitlab-ci-runner', '= 1.2.0', :supermarket
knife supermarket install gitlab-ci-runner
knife supermarket download gitlab-ci-runner
Quality 44%

Gitlab CI Runner


Install and configure runners for gitlab-ci. Use gitlab-ci-multi-runner as runner type. Learn more on


Cookbooks and gems

Declared in [metadata.rb](metadata.rb) and in [Gemfile](Gemfile).


  • RHEL Family 7, tested on Centos

Note: it should work fine on Debian 8 but the official docker image does not allow systemd to work easily, so it could not be tested.


Easy Setup

Add recipe[gitlab-ci-runner] in your run-list to install gitlab-ci-multi-runner using its repository.

To add runners, use default provider or use recipe[gitlab-ci-runner::register] and runners attribute. To see a use case, look at [.kitchen.yml](.kitchen.yml).


This cookbook is fully tested through the installation of the full gitlab platform in docker hosts. This uses kitchen, docker and some monkey-patching.

If you run kitchen list, you will see 2 suites, Each corresponds to a different server:

  • gitlab-ubuntu-1404: complete instance of gitlab (official docker image)
  • runner-centos-7: installation of gitlab-ci-multi-runner and configuration of runners

For more information, see [.kitchen.yml](.kitchen.yml) and [test](test) directory.


Configuration is done by overriding default attributes. All configuration keys have a default defined in [attributes/default.rb](attributes/default.rb). Please read it to have a comprehensive view of what and how you can configure this cookbook behavior.



Install gitlab-ci-multi-runner by using its repository, enable and start the service.


Install runner repository.


Install gitlab-ci-multi-runner package.


Enable and start runner service.


Register or Unregister runners based on attribute ['gitlab-ci-runner']['runners']. This is an Array of Hash where each Hash represent an action on a runner, "register" or "unregister". In a Hash, description key is the name attribute and represents the name of the runner. Then each runner option should be listed in a sub-Hash of key options, each sub-key matching an option name of gitlab-runner cli.

See [.kitchen.yml](.kitchen.yml) for an example.



Register or Unregister runners. For instance, to register a default runner to http://gitlab-ci.myinstance:

gitlab_ci_runner 'my runner' do
  options {
    registration_token: '1234567890',
    url: 'http://gitlab-ci.myinstance'

The options list with full documentation is available in [resources/default.rb](resources/default.rb).


Available in [](


Please read carefully []( before making a merge request.

License and Author

Copyright (c) 2015-2016 Sam4Mobile

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
See the License for the specific language governing permissions and
limitations under the License.

Dependent cookbooks

yum >= 0.0.0

Contingent cookbooks

There are no cookbooks that are contingent upon this one.




  • Fix #2: multiple tags are now correctly handled
  • Fix #3: ruby_block resource is always run
  • Fix #6: Make repo URL and gpgkey an attribute
  • Fix #7: Support multiple env strings
  • Add ChefSpec matchers for LWRP


  • Switch to kitchen-docker_cli instead of kitchen-docker
  • Clean kitchen.yml, use instance names & add skip_preparation
  • Add tags in gitlab-ci tests
  • Use Continuous Integration with gitlab-ci
  • Can specify retries in package, set 1 in tests



  • Fix cookbook to work with latest available version of gitlab (8.5) and gitlab-runner (1.0.4)
  • Be completely generic and accept any runner options
    • rename token to registration_token to match runner cli option name


  • Change kitchen driver to docker_cli
  • Use official docker image for gitlab
  • Remove useless monkey patching


  • Fix all rubocop offenses
  • Add license, refactor README and update it
  • Add default attribute 'runners' with a small documentation


  • Initial version with Centos 7 support

Collaborator Number Metric

1.2.0 failed this metric

Failure: Cookbook has 1 collaborators. A cookbook must have at least 2 collaborators to pass this metric.

Contributing File Metric

1.2.0 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of, and your repo must contain a file

Foodcritic Metric

1.2.0 failed this metric

FC066: Ensure chef_version is set in metadata: gitlab-ci-runner/metadata.rb:1
FC069: Ensure standardized license defined in metadata: gitlab-ci-runner/metadata.rb:1
Run with Foodcritic Version 10.3.1 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

License Metric

1.2.0 passed this metric

No Binaries Metric

1.2.0 passed this metric

Publish Metric

1.2.0 passed this metric

Supported Platforms Metric

1.2.0 passed this metric

Testing File Metric

1.2.0 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of, and your repo must contain a file

Version Tag Metric

1.2.0 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of, and your repo must include a tag that matches this cookbook version number