Skip to content

Bump gitlab-exporter to 10.3.0

Matthias Käppler requested to merge mk-gitlab-exporter-10.3 into master

What does this MR do?

This updates the gitlab-exporter service to the latest version 10.3.0, which in return updates Puma to the latest available version 5.3.2.

Related issues

General maintenance.

Test plan

The changes in this branch have been applied to the Docker image tagged 13.12.2-rfbranch.316148703.ff48e6e5-0.

  1. Start a container from 13.12.2-rfbranch.316148703.ff48e6e5-0
  2. Edit gitlab.rb and set both gitlab_exporter['enable'] = true and gitlab_exporter['server_name'] = 'puma'
  3. Run gitlab-ctl reconfigure
  4. Run gitlab-ctl tail gitlab-exporter

You should see Puma v5.3.2 running:

2021-06-08_12:53:09.33910 == Sinatra (v2.0.8.1) has taken the stage on 9168 for development with backup from Puma
2021-06-08_12:53:09.33925 Puma starting in single mode...
2021-06-08_12:53:09.33925 * Puma version: 5.3.2 (ruby 2.7.2-p137) ("Sweetnighter")
2021-06-08_12:53:09.33925 *  Min threads: 0
2021-06-08_12:53:09.33926 *  Max threads: 5
2021-06-08_12:53:09.33926 *  Environment: development
2021-06-08_12:53:09.33926 *          PID: 1174
2021-06-08_12:53:09.33945 * Listening on http://127.0.0.1:9168
2021-06-08_12:53:09.34127 Use Ctrl-C to stop

Checklist

See Definition of done.

For anything in this list which will not be completed, please provide a reason in the MR discussion

Required

  • Merge Request Title, and Description are up to date, accurate, and descriptive
  • MR targeting the appropriate branch
  • MR has a green pipeline on GitLab.com
  • Pipeline is green on dev.gitlab.org if the change is touching anything besides documentation or internal cookbooks
  • [-] trigger-package has a green pipeline running against latest commit Note: I was able to build an image; QA test failures do not apply because gitlab-exporter is not targeted by those tests.

Expected (please provide an explanation if not completing)

Edited by Matthias Käppler

Merge request reports