- Issue created by @maxwhitehead
- Merge request !11725Issue #3517217: Use drupalci image `webdriver-chromedriver` instead of `chromedriver` (don't use stale image) → (Open) created by maxwhitehead
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.
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`.
Update core CI references from `$_CONFIG_DOCKERHUB_ROOT/chromedriver:production` to `$_CONFIG_DOCKERHUB_ROOT/webdriver-chromedriver:production`
Update core CI references from `$_CONFIG_DOCKERHUB_ROOT/chromedriver:production` to `$_CONFIG_DOCKERHUB_ROOT/webdriver-chromedriver:production`
Fix CI chromedriver image reference to use updated image
Active
11.0 🔥
other
