Closed Bug 929147 Opened 10 years ago Closed 5 years ago

[meta] Optimize chrome application build

Categories

(Firefox Build System :: General, defect)

Product:
Firefox Build System
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: gps, Unassigned)

References

(Depends on 1 open bug)

Details

(Keywords: meta) 

We have a quarterly goal to optimize the building of chrome applications. We should cut down on build actions/rules without dependencies, make no-op/light builds as fast as possible, etc.
Depends on: 924617, 487182
Depends on: 915804, 924187
No longer depends on: 487182
Bug 487182 is about JarMaker creating jars itself, which we're not using anymore. JarMaker always do flat files now (except a few things, but they are too few to care)
Depends on: 774572
Depends on: 948843
Depends on: 955604
Product: Core → Firefox Build System
Between artifact builds and `mach build faster` this is pretty good nowadays.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.