Don't regenerate build ID for every build on developer machines




Build Config
a year ago
2 months ago


(Reporter: ted, Unassigned)


(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)




a year ago
Currently if you do a top-level build, even if it's a no-op, we generate a new build ID and then wind up re-linking the firefox binary because of that. This is important for automation (so that the generated binaries have a correct build ID), but not really for local builds. The FORCE rules are here:

When discussing this on IRC, glandium pointed out that we depend on this behavior to invalidate some caches (I have forgotten exactly what), but perhaps that's no longer true or if so we can find a smarter way to do this that doesn't involve doing this work for a no-op build.

Comment 1

a year ago
Oh! We do already have a different workaround for this:

We touch dist/bin/.purgecaches, which is intended to have the same effect.


a year ago
Blocks: 1297386
I'm not sure .purgecaches does all the necessary work.
Also, relinking the firefox binary isn't really /that/ time consuming. The other bugs blocking bug 1297386 take a lot more time.
I agree other bugs are more important from an impact perspective. But the principle of the matter is that if nothing changes the build should be a no-op. In fact, I believe Tup will reach this conclusion on its own and skip linking if none of the input files change. So we'll need to figure out cache purging eventually. Might as well do it in this bug.
I'll repeat what I've said repeatedly: no-ops are uninteresting. Nobody does a no-op. There is always something changing. The problem is it is very hard to know what change needs a buildid update. So we update it all the time. Ensuring Firefox doesn't require a buildid bump besides having the number updated is not a build system problem. It's a platform + Firefox problem.
If a Firefox developer changes a .jsm linked by a, why do we need to relink firefox.exe? I contend we should never have to relink firefox.exe in that scenario.
We shouldn't, but if we don't, we can't guarantee it won't be broken. Again, providing that guarantee is a platform + Firefox problem, not a build system problem.

Comment 8

a year ago
If .purgecaches doesn't work reliably we should fix it so it does.
Another option is to disable MOZ_APP_STATIC_INI on local builds.
Tup itself doesn't track the clock as an input, so last time I built Firefox with it (~2013?), I generated the buildid / application.ini.h in mach before running tup. So as far as tup was concerned, some files had always changed even on a "no-op" build, and so it always ran the commands that depended on them. The nsBrowserApp.cpp / firefox chain takes less than a second, so I agree its fairly low on the priority list.

The main problem I ran into is that tup automatically picks up the dependency from buildid.h to libxul, which we currently lie about in the Makefile:

If you fix that dependency, you can see that does indeed change on every build since the buildid used by nsAppRunner changes. Would it affect anything if we changed nsAppRunner's buildid for local builds to be something static? Should we grab someone knowledgeable from platform to see what other options we have?

Comment 11

2 months ago
This came up in discussion again today in re: tup. I posit that this *must* work OK, because artifact builds work, and those do not rebuild the firefox binary.
The point is that any binary change is accompanied with a buildid change.
You need to log in before you can comment on or make changes to this bug.