Hi,
When I dynamically create review environments like this:
reviewEnv:
script:
- env
- exit 0
environment:
name: review/${CI_COMMIT_SHORT_SHA}
url: https://${CI_COMMIT_SHORT_SHA}.hash.works
The created environment will not have the “External URL” set to $CI_ENVIRONMENT_URL, resulting in no buttons to jump to the new review deployment.
However, when I use a subdomain that actually exists and resolves this works just fine:
reviewEnv:
script:
- env
- exit 0
environment:
name: review/${CI_COMMIT_SHORT_SHA}
url: https://fb.hash.works
It seems that GitLab checks if the URL is actually reachable. My problems are that A) our GitLab server needs a webproxy to access external HTTP-Endpoints and B) its DNS server might not even resolve the used domain. The browsers of our developers however might reach that URL just fine.
How can I tell GitLab not to check if the environment URL is actually reachable?
Best Regards