Update to Chrome 74

[steebchen]

This version of ChromeDriver only supports Chrome version 74

current chrome installed in this docker image is v73.x

[everflux]

Should be fixed in the :latest tag.
Unfortunately protractor/chrome-webdriver is bumping the required minimum chrome version while beeing kept up-to date, so a build can start to fail without any changes. I don't see how a permanent fix could work due to the implementation of the chrome-webdriver update mechanism. Only option is to build a new image with the latest chrome/chromium version.

[steebchen]

Thanks! Maybe you could setup a build once per day somehow and push to latest? GH actions can schedule builds. If not I'll probably fork it and set it up myself in the long term.

[everflux]

Even once per day will not completely solve the problem, since the release of a newer webdriver/chromebrowser can happen at any time and will break your build in the angular context.
The underlying problem is the automatic behaviour of the webdriver-manager and they themself have this issue in their tracker at regular intervals:
angular/webdriver-manager#376
angular/webdriver-manager#373
angular/webdriver-manager#358
angular/webdriver-manager#353
angular/webdriver-manager#328

To me it looks deeply broken (by design) and there is not to do from the docker image point of view, but of course more regular builds might shadow the real problem. (Currently in the Angular 8 phase, there are not much angular-cli versions coming, which drove more regular builds in the past.)

[steebchen]

Hm.. I agree. I think I'll just update chrome every time to fix the problem for now (e2es are slow anyway, the extra chrome update won't matter for me).