Closed Bug 1159960 Opened 11 years ago Closed 11 years ago

[fxos-automation] Add support for taskcluster npm-cache in gecko

Categories

(Taskcluster :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: aus, Assigned: aus)

References

Details

Attachments

(2 files, 1 obsolete file)

We are using the new npm-cache mechanism for everything gaia but we really should turn this on for gecko ASAP.
Current big hopes and dreams is to have this ready'ish by Friday to test over the weekend and deploy to all on Monday or Tuesday. :)
Things that need to happen to make this work: * Update mozharness (https://hg.mozilla.org/build/mozharness/file/cf3b33c04c78/mozharness/mozilla/gaia.py) to use NODE_MODULE_SRC=npm-cache. * Update gecko mozharness revision http://mxr.mozilla.org/mozilla-central/source/testing/mozharness/mozharness.json * Add taskcluster-npm-cache to the global node modules installed in the docker worker image (http://mxr.mozilla.org/mozilla-central/source/testing/docker/tester/Dockerfile) * Bump VERSION (http://mxr.mozilla.org/mozilla-central/source/testing/docker/tester/VERSION) The most annoying part is actually making the new version of mozharness testable since it's pulled from from a specific place with a specific revision. I'm expecting I will need to setup a branch for this ASAP.
Attachment #8604953 - Flags: review?(jlal)
Attachment #8600532 - Attachment is obsolete: true
Attachment #8600532 - Flags: review?
Attachment #8604956 - Flags: review?(jgriffin)
Comment on attachment 8604953 [details] [diff] [review] Patch - v1 - Update tester docker image lgtm... Lets try to land the version bump ASAP
Attachment #8604953 - Flags: review?(jlal) → review+
Comment on attachment 8604956 [details] [diff] [review] Patch - v1 - Update mozharness to use taskcluster-npm-cache Review of attachment 8604956 [details] [diff] [review]: ----------------------------------------------------------------- This looks good from a mozharness perspective. I don't know how the npm cache works, so can't vouch for that part.
Attachment #8604956 - Flags: review?(jgriffin) → review+
New tester docker image deployed to quay.io: rev [fbc904cd326b] on {https://quay.io/v1/repositories/mozilla/tester/tags/0.3.1}.
Hello, I see mullet failures since this landed. Can you take a look if it's caused by the update?
Bam! Version conflict errors I think.... Can you rebase this and vbump again and try with a mulet push as well?
This is still busted on re-landing.
seems this got backed out again aus ?
Flags: needinfo?(aus)
(In reply to Carsten Book [:Tomcat] from comment #17) > seems this got backed out again aus ? Yes, I was still seeing some failures. I re-based just now and will attempt to push again.
Flags: needinfo?(aus)
OK. Let's hope the change sticks this time. :)
Looks like this is all happy and running as expected. I'm going to go ahead and mark this fixed. :)
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Component: TaskCluster → General
Product: Testing → Taskcluster
Target Milestone: --- → mozilla41
Version: unspecified → Trunk
Resetting Version and Target Milestone that accidentally got changed...
Target Milestone: mozilla41 → ---
Version: Trunk → unspecified
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: