1112915 - [fxos-automation] Create docker image to handle npm caching.

Status: RESOLVED FIXED

(Taskcluster :: General, defect)

Description

[James Lal [:lightsofapollo]]

The approach I am going to take here looks like this:

  - The "extra" category will be used to specify the npm package.json

  - Index service will be used but explicitly rather then via routes so we can ensure read-after-create consistency.

  - The image itself will decide how to name the index based on a combination of the hash of the package.json + node major version (0.10 vs 0.12, etc...) + os

  - The image itself will perform some sanity validation as needed (and generally disallow configuration aside from what is defined in extra)

Comment 1

[James Lal [:lightsofapollo]]

not actively working on this but aus is doing stuff

Aus you want to assign yourself?

Comment 2

[Aus Lacroix [:aus]]

Yep, I'll end up taking care of this. I don't know that we have the ability to generate docker images on the fly right now though, isn't this something we'd need first to get this done in an ideal manner?

I was envisioning this as our end game -- we'll have a taskgraph we can run to generate what's required to get to a buildable + testable state (update repo to desired revision, update npm cache, run npm install). At this point, we could generate a new docker image that will be used to run the build + test steps. This image will be able to assume it doesn't require any updates, it can skip directly to building the gaia profile and running the test chunks it's responsible for. I'll create a meta bug to track this task and others like it for optimizing build/test run times.

Adding the npm cache task is tracked in bug 1141792.

Comment 3

[Aus Lacroix [:aus]]

This is fixed. We've landed an npm-cache docker worker image a while back. Just forgot to close this.

see hub.docker.com -- taskcluster/npm-cache

Comment 4

[Pete Moore [:pmoore][:pete]]

Resetting Version and Target Milestone that accidentally got changed...