Contrib.social

CI: Using stale drupalci chromedriver image (`chromedriver` is stale, `webdriver-chromedriver` gets updates)

Open on Drupal.org →
Created on 3 April 2025, about 1 month ago

Problem/Motivation

When migrating drupalci_environments → images from dockerhub to gitlab.com registry, noticed that core CI is using drupalci `chromedriver` image.

At some point the drupalci image build processed changed, changes to chromedriver only go to the image titled `webdriver-chromedriver` (last touched 1 year ago), `chromedriver` image is last touched >2 years ago.

Doubtful this is causing any issues, but probably would make sense to update.

Steps to reproduce

Can compare timestamp of production tag of these two images on dockerhub (https://hub.docker.com/r/drupalci/webdriver-chromedriver/tags, https://hub.docker.com/r/drupalci/chromedriver/tags). Though we now use registry at https://gitlab.com/drupal-infrastructure/drupalci/drupalci-environments/... (but all images were synced over yesterday so timestamps don't communicate it).

Otherwise I reviewed drupalci_environments build CI, and it pushes to `webdriver-chromedriver`.

Proposed resolution

Update core CI references from `$_CONFIG_DOCKERHUB_ROOT/chromedriver:production` to `$_CONFIG_DOCKERHUB_ROOT/webdriver-chromedriver:production`

Remaining tasks

Update core CI references from `$_CONFIG_DOCKERHUB_ROOT/chromedriver:production` to `$_CONFIG_DOCKERHUB_ROOT/webdriver-chromedriver:production`

Release notes snippet

Fix CI chromedriver image reference to use updated image

📌 Task
Status

Active

Version

11.0 🔥

Component

other

Created by

🇺🇸United States maxwhitehead

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024