Docker Images tag for browser versioning

[zhilyaev]

🚀 Feature Proposal

Browser versioning

Motivation

Testing with different browser version

Example

docker pull selenium/node-chrome:v78.0
docker pull selenium/node-chrome:v77.0
docker pull selenium/node-firefox:v71.0

Java

DesiredCapabilities capabilities = new DesiredCapabilities();
capabilities.setBrowserName("chrome");
capabilities.setVersion("78.0");

Docker-compose

version: '2'
services:

  chrome-64:
    container_name: chrome
    image: selenium/node-chrome:v64.0
    volumes:
      - /dev/shm:/dev/shm
    depends_on:
      - hub
    environment:
      HUB_HOST: hub
      
  chrome-78:
    container_name: chrome
    image: selenium/node-chrome:v78.0
    volumes:
      - /dev/shm:/dev/shm
    depends_on:
      - hub
    environment:
      HUB_HOST: hub

  hub:
    container_name: selenium
    image: selenium/hub
    ports:
      - "4444:4444"

[diemol]

I think this is a good idea, and I was thinking something along the same lines.
What I am trying to figure out is:

• There are usually minor browser versions after the initial major release, how would we handle that? Should we have the full browser version as a tag?
• Do we need to mention the browser driver version somewhere in the tag?
• Could we say for standalone something like selenium/standalone-chrome:v78.0? How do we mention the Selenium Grid version placed there?

What are your thoughts @zhilyaev?

[zhilyaev]

Tag is flexible tool.

Base

• selenium:{GRID_VERSION}
• selenium:{GRID_VERSION}-{NAME}

Node Base

• selenium/node:{GRID_VERSION}
• selenium/node:{GRID_VERSION}-{NAME}

Hub

• selenium/hub:{GRID_VERSION}
• selenium/hub:{GRID_VERSION}-{NAME}

Node & Standalone

That's like maven:3.6.1-jdk-8-alpine or like selenoid :

• selenium/{BROWSER_NAME}:{BROWSER_VERSION}-grid-{GRID_VERSION}-{NODE|STANDALONE}

• selenium/{BROWSER_NAME}:{BROWSER_VERSION}-grid-{GRID_VERSION}-{NODE|STANDALONE}-{DEBUG}

• selenium/chrome:80.0-grid-3.149.59-node

  • Options try use alias:
  • selenium/chrome:80.0-grid-3
  • selenium/chrome:80.0
  • selenium/chrome:latest

• selenium/chrome:80.0-grid-3.149.59-standalone-debug

  • alias selenium/chrome:80.0-grid-3-standalone-debug

• selenium/chrome:80.0-grid-3.149.59-node-debug

[zhilyaev]

Or

• selenium/node-{BROWSER_NAME}:{BROWSER_VERSION}-grid-{GRID_VERSION}-{DEBUG}
• selenium/standalone-{BROWSER_NAME}:{BROWSER_VERSION}-grid-{GRID_VERSION}-{DEBUG}

[ddavison]

I think this would be awesome to have. 👍

We should be able to enumerate stable versions, then have our Makefile tag the versions, but i'm not sure the :v77 strategy will be best.

Perhaps something like:

selenium/node-chrome-chrome77:3.149.59
selenium/node-firefox-firefox72.0.2:3.141.59

selenium/node-chrome-chrome77-chromedriver77

to tag specific versions of software packaged within, while still maintaining the Selenium version.

It's verbose, but it works. GitLab uses a similar automated packaging technique.

[diemol]

Fixed by #1086
Also adding the pushed images into the release notes (Automating this is work in progress)
https://github.com/SeleniumHQ/docker-selenium/releases/tag/4.0.0-alpha-6-20200720