[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:
Blocks
blocks UXPROD-1821 3rd party dependency upgrades (Q4 2019) Closed
blocks UXPROD-2214 3rd party dependency upgrades (Q1 2020) Closed
Relates
relates to FOLIO-2115 Consider replacing Chrome with Chromi... Open
relates to FOLIO-2156 Pin the version of ansible in Jenkins... Closed
relates to FOLIO-1940 Update Jenkins docker build image Closed
relates to FOLIO-2108 Improve lint-raml for parsing YAML, a... Closed
relates to FOLIO-2174 Spike: Identify tasks related to upda... Closed
Sprint:
Development Team: FOLIO DevOps

 Description   

This is part one of the larger task (i.e. FOLIO-1940 Closed to update all tools provided by the "jenkins-slave-all" docker build image).

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 ( FOLIO-2115 Open ).

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) – FOLIO-2156 Closed .

4) Use Chromium rather than Chrome – FOLIO-2115 Open .



 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.

Generated at Thu Feb 08 23:18:46 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.