You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue:
When we are running the build on CICO, we get chrome version 65 and web driver 2.33 is not working with that which fabric8-planner needs for functional testing. Hence we need updated web driver which is not supported for chrome 62 (that we get while running the build on f8.jenkins)
Theory:
The current stable version of google-chrome is 65.* see wiki
The web driver is 2.33 which we are using for functional tests in the planner here.
This line installs the latest stable chrome version. The master branch and hence the image was last built in October and pushed here https://hub.docker.com/r/fabric8/fabric8-ui-builder/tags/.
tag v3c57d6b is being used in the fabric8-pipeline while creating fabric8UITemplate
We use this container while running planner CI here. Hence we always get chrome version 62.*
Solution:
Trigger a new build for this repo, and push it to docker like we did last time. Use the new tag in fabric8-pipeline. So that planner build will get latest chrome 65 and we can use updated chrome-driver.
Future:
We may face the same problem in future after 5-6 months when new chrome version and old web driver is not compatible with planner's functional tests.
We have 4 projects and 4 libraries using this to build with. I'm not aware of anything that would break with the upgrade but it is something you should test.
Issue:
When we are running the build on CICO, we get chrome version 65 and web driver 2.33 is not working with that which fabric8-planner needs for functional testing. Hence we need updated web driver which is not supported for chrome 62 (that we get while running the build on f8.jenkins)
Theory:
The current stable version of google-chrome is 65.* see wiki
The
web driver is 2.33
which we are using for functional tests in the planner here.This line installs the latest stable chrome version. The
master
branch and hence the image was last built in October and pushed here https://hub.docker.com/r/fabric8/fabric8-ui-builder/tags/.tag
v3c57d6b
is being used in the fabric8-pipeline while creating fabric8UITemplateWe use this container while running planner CI here. Hence we always get chrome version 62.*
Solution:
Trigger a new build for this repo, and push it to docker like we did last time. Use the new tag in fabric8-pipeline. So that planner build will get latest chrome 65 and we can use updated chrome-driver.
Future:
We may face the same problem in future after 5-6 months when new chrome version and old web driver is not compatible with planner's functional tests.
Who gets affected:
All those projects using fabric8UITemplate.groovy might be affected
The text was updated successfully, but these errors were encountered: