I have a build that works locally, but on gitlab it fails. Even though I have a rule to poll for http availability, when the test starts I get Connection refused again. Any idea what this might be?
Locally the build can run with
export GITLAB_CONTAINER_TAG=gitlab/gitlab-ce:latest gradle test
- GitLab Version: gitlab.com, gitlab/gitlab-ce:latest in CI
- Add the CI configuration from
.gitlab-ci.ymland other configuration if relevant (e.g. docker-compose.yml)
I checked several way to wait for the container to be running, using the healthcheck, no configuration and checking if /projects responds with http 200. They all work locally, but on gitlab.com they fail.
I am now also printing the logs of the container, so perhaps within those logs it can be seen what the issue might be / if the server somehow shuts down again?