Depending on the CI infrastructure setup one may need to run the ATH itself in a docker container with access to the host docker service, following a strategy similar to the one described in this article. When this is needed, the docker fixtures should not be accessed through mapped ports on the docker host, but directly through their container IP and port since they are "sibling" containers to the ATH. To enable this, set the environment variable SHARED_DOCKER_SERVICE=true, and then the functions ipBound(n) and port(n) will just return the container's IP and port where the fixture can be accessed.
TO-DO: Instead of depending on setting this environment variable, in the future we could try to somehow automatically detect the situation.
Interactive shell:
harry@devbox $ ./ath-container.sh
ath-user@0b968f00a942:~$ eval $(./vnc.sh)
ath-user@0b968f00a942:~$ ./run.sh firefox latest -Dmaven.test.failure.ignore=true -DforkCount=1 -B -Dtest=...
Jenkinsfile:
See the repository Jenkinsfile for inspiration.