This instance will be upgraded to Heptapod 0.26.0rc1 on 2021-10-25 at 14:00 UTC+2 (a few minutes of down time)

Commit 9386709b authored by Georges Racinet's avatar Georges Racinet 🦑
Browse files

Heptapod CI inside: avoiding chromedriver from Ubuntu Snap

With the upgrade of the base Heptapod Docker image to Ubuntu 20.04
in the wake of moving to GitLab 13.9 comes the fact that the whole
chromium suite is now available as snaps only. No big surprise that
the selenium tests launched from inside the Docker container don't
work: the container is not even privileged in our setup (and it

To work around this, we're now installing chromedriver from a PPA.
For automated, sandboxed, testing, this is tolerable.

A longer term move would be to re-explore the possibility to use
the Firefox driver.
parent 1d18e6772e46
Pipeline #18341 failed with stages
in 20 seconds
......@@ -49,13 +49,22 @@ docker-inside:
- apt-get update
- apt-get -y install sudo
# for PPA management
- apt-get -qy install sudo software-properties-common
- visudo --file=ci/omnibus.sudoers -c
- install -m 0440 -o root -g root ci/omnibus.sudoers /etc/sudoers.d/omnibus
- |
cat > /etc/apt/preferences <<EOF
Package: *
Pin: origin ""
Pin-Priority: 700
- add-apt-repository ppa:saiarcot895/chromium-beta -y
- apt-get -qy install chromium-chromedriver
- ln -s /usr/lib/chromium-browser/chromedriver /usr/bin/
# this will in particular bring a version of virtualenv that's suited
# for Python 3.8 instead of one that can't use Python 3.8 in --python option
- /opt/gitlab/embedded/bin/pip3 install tox
- apt-get -y install chromium-driver
- ci/run-tests-inside || ci/fail-copy-logs
when: on_failure
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment