Gitlab is hosted on ARO, which is behind firewall.

Now when pipeline is run then gitlab tries to download the plugins/dependencies from public internet (which is central repo).

So now the firewall blocks gitlab from connecting to the internet and pipeline fails. Even if we modify settings.xml the central repo won’t be acfessible.

Now problem two-folds as Gitlab creates a dynamic runner when the pipeline is triggered, so it gets assigned a dynamic ip. So even if we whitelist the ARO subnet ip, the gitlab server is not able to pull through the central repo on Internet.

Gitlab is hosted on ARO, which is behind firewall.

Now when pipeline is run then gitlab tries to download the plugins/dependencies from public internet (which is central repo).

So now the firewall blocks gitlab from connecting to the internet and pipeline fails. Even if we modify settings.xml the central repo won’t be acfessible.

Now problem two-folds as Gitlab creates a dynamic runner when the pipeline is triggered, so it gets assigned a dynamic ip. So even if we whitelist the ARO subnet ip, the gitlab server is not able to pull through the central repo on Internet. I need a solution for above problem