Build of Kumascript Docker image sometimes does not pick-up latest mdn-browser-compat-data npm package

RESOLVED FIXED

Status

Mozilla Developer Network
KumaScript
P1
normal
RESOLVED FIXED
a month ago
a month ago

People

(Reporter: rjohnson, Assigned: rjohnson)

Tracking

Details

(Whiteboard: [specification][type:bug])

(Assignee)

Description

a month ago
What did you do?
================
1. Changes submitted to master
2. Jenkins build starts
3. Build fails (for any reason)
4. New version of mdn-browser-compat-data released
5. Re-build started

What happened?
==============
The Docker image re-build uses the cached build layers so the "npm update" is not re-run, and the latest version of "mdn-browser-compat-data" is not picked-up

What should have happened?
==========================
The latest version of "mdn-browser-compat-data" should have been picked-up and embedded in the Kumascript Docker image

Is there anything else we should know?
======================================
No.
(Assignee)

Updated

a month ago
Assignee: nobody → rjohnson

Comment 1

a month ago
Commits pushed to master at https://github.com/mozilla/kuma

https://github.com/mozilla/kuma/commit/230ea3edb2369973bd97684a3e7e370571c514e4
bug 1409119: do not use cached layers when building ks image

* the purpose of this is to ensure that the "npm update" command
  is always run so that updates to the "mdn-browser-compat-data"
  are always picked-up

https://github.com/mozilla/kuma/commit/833f501e0d78b48e8ea1294bf0364dcd2a5b0fe5
Merge pull request #4465 from escattone/ks-docker-build-no-cache-1409119

bug 1409119: do not use cached layers when building ks image
Status: NEW → RESOLVED
Last Resolved: a month ago
Priority: -- → P1
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.