Skip to content

Prevent logging every connection to the instance when using an autoscaler

What does this MR do?

Hide verbose messages about connection to an instance when running gitlab-runner in an autoscaler mode.

There are more messages that could be hidden, or a new 1-time message could be added about the connection details for the instance, but I first want to know if this MR would make sense 😄

Why was this MR needed?

in !3783 (merged), some extra logging was added about the connection to the instance running the job.

As there are multiple connections set up, this info is repeated over and over again, without (IMO) direct added value.
This results in less readable CI output, see screenshots below.
Depending on the situation, there are even more dialing instance... and instance ... connected messages

before MR 3783
before

after MR 3783
after

What's the best way to test this MR?

  • configure a gitlab-runner using an autoscaler (we're using fleeting on GCP)
  • run a simple hello-world CI job, this should have somehow similar output as the before screenshot
  • apply the MR and compile the gitlab-runner binary, and restart the process
  • run the same CI job again, this should have somehow similar output as the after screenshot

What are the relevant issue numbers?

Merge request reports