[FOLIO-2115] Consider replacing Chrome with Chromium in Jenkins docker build image Created: 26/Jun/19 Updated: 03/Jun/20 |
|
| Status: | Open |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | TBD |
| Reporter: | David Crossley | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | devops, platform-backlog | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||
| Sprint: | |||||||||||||
| Development Team: | Core: Platform | ||||||||||||
| Description |
|
To prepare for
(We use Chrome for the headless browser tests via Karma.) However test builds of jenkins-slave-all show a problem with the current version of Chrome (v75) being included here. Only the current version of "google-chrome-stable" is available, so we cannot pin to a previous version. Instead using "chromium-browser" (current release v74) is successful. If ever needed, we would be able to pin to a previous version. |
| Comments |
| Comment by David Crossley [ 27/Jun/19 ] |
|
We could await the next version of Chrome and see how that fares. Also we have not yet attempted to fully explore the reasons for this failure. At this stage it is not urgent, so we can continue with this old version of Chrome (71.0.3578). An alternative solution could be to utilise Chromium instead. Zak Burke would that be a possibility, or do we need to remain with Chrome? |
| Comment by Zak Burke [ 01/Jul/19 ] |
|
Yes, let's use Chromium. It is essentially the chassis Chrome is built upon so I don't foresee any issues. The general guidance from the PC has been to get things running in one browser for now with the understanding that eventually we'll need to support more than one. This may be a good time to consider adding additional browsers to the testing pipeline, but that's a separate issue. |