[FOLIO-2175] Update Jenkins docker build image: part 1 Created: 18/Jul/19 Updated: 29/Jul/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: | FOLIO DevOps | ||||||||||||||||||||||||||||||||||||
| Description |
|
This is part one of the larger task (i.e.
For the past few months we have not been able to rebuild the image. Its Dockerfile (at folio-tools/jenkins-slave-docker/Dockerfile) does pin some tools to specific versions, while others will automatically become the latest available. That is generally okay. However one situation is preventing a rebuild. Chrome is only available as its most recent version, and when we try to rebuild jenkins-slave-all image, then the invocation of Karma for regression tests fails with that Chrome. Our tests do show that using the current Chromium instead is fine (
Therefore we cannot update Chrome, other supporting tools such as aws-cli, and the other items from our folio-tools such as lint-raml and generate-api-docs. This first part is intended to regain the ability to rebuild the image more frequently. The complete upgrade can then happen later. The strategy is: 1) Leave the base OS image as-is (ubuntu:xenial). Leave other pinned tools as-is. 2) Update Yarn pinned version to be more recent. 3) Pin Ansible to the version that we currently use (2.7.x) –
4) Use Chromium rather than Chrome –
|
| Comments |
| Comment by John Malconian [ 23/Jul/19 ] |
|
David Crossley - I think we should investigate moving the base OS image from Ubuntu 16 to Ubuntu 18 as part of this. |
| Comment by David Crossley [ 31/Jul/19 ] |
|
The reason that i suggested to not upgrade the base OS, was to expedite this Part 1. Then follow on later with that and other stuff as Part 2. |