Closed Bug 1567134 Opened 5 years ago Closed 5 years ago

ESLint builders are downloading modules from npm

Categories

(Developer Infrastructure :: Lint and Formatting, defect, P1)

defect

Tracking

(firefox-esr60 unaffected, firefox-esr68 unaffected, firefox68 unaffected, firefox69 unaffected, firefox70 fixed)

RESOLVED FIXED
mozilla70
Tracking Status
firefox-esr60 --- unaffected
firefox-esr68 --- unaffected
firefox68 --- unaffected
firefox69 --- unaffected
firefox70 --- fixed

People

(Reporter: standard8, Assigned: standard8)

References

(Blocks 1 open bug, Regression)

Details

(Keywords: regression)

Attachments

(1 file)

I just noticed that bug 1564138 changed the top-level package.json, and that's caused the ESLint builders to download directly from npm.

We should fix the fundamental issue, for which I've filed bug 1567132. I probably won't have time for that for a couple of weeks.

In the meantime, I'll post the quick patch to update the builders properly and get us in a good state again.

Bugbug thinks this bug is a defect, but please change it back in case of error.

Type: task → defect
Pushed by mbanner@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/10264d61e544
Update the node modules packages for the builders. r=ahal

Does npm have a flag like cargo's --frozen, that prevents it from downloading stuff?

(In reply to Mike Hommey [:glandium] from comment #4)

Does npm have a flag like cargo's --frozen, that prevents it from downloading stuff?

Not that I can see. Once we get to vendoring, we shouldn't have this problem. In the meantime, bug 1567132 should be an easy way to prevent this happening (I'm just out from today for a week, so haven't had time).

(In reply to Mark Banner (:standard8) (afk 19th - 28th July) from comment #5)

(In reply to Mike Hommey [:glandium] from comment #4)

Does npm have a flag like cargo's --frozen, that prevents it from downloading stuff?

Not that I can see. Once we get to vendoring, we shouldn't have this problem. In the meantime, bug 1567132 should be an easy way to prevent this happening (I'm just out from today for a week, so haven't had time).

Actually, bug 1567132 is probably the main issue here. We shouldn't be running npm install/ci on the builders as we already have node_modules unpackaged.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla70
Has Regression Range: --- → yes
Product: Firefox Build System → Developer Infrastructure
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: