Skip to content

Enable FF_NETWORK_PER_BUILD=true for all vendored gems

Stan Hu requested to merge sh-enable-ff-network-per-build into master

What does this MR do and why?

In #460842 (closed), we discovered that the legacy mechanism for linking Docker containers via the --link argument assigns both IPv4 and IPv6 addresses. Since the experimental IPv6 option is not enabled in Docker, talking to network services incurs about a 1-second delay as the network falls back to IPv4.

To avoid this, we should switch on FF_NETWORK_PER_BUILD=true, which is the default setting in our private runners. This ensures only IPv4 addresses are used.

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After

How to set up and validate locally

I did a quick test:

  1. Removed FF_NETWORK_PER_BUILD from the CI/CD variables.
  2. Hit retry on a build: https://gitlab.com/gitlab-org/gitlab/-/jobs/6812731585
  3. Validated this has FF_NETWORK_PER_BUILD=true.
Edited by Stan Hu

Merge request reports

Loading