Creating Nightly or "on change" builds for Prism



Release Engineering
10 years ago
5 years ago


(Reporter: mfinkle, Unassigned)


Firefox Tracking Flags

(Not tracked)


It would be really great to get Prism builds on code changes or even a nightly build for Windows, Linux and Mac.
Mark, can you please give us the basic steps to:

* check out 
* build 
* package

From discussion earlier it sounds like this would pull the latest xulrunner nightly SDK from

I think that building/publishing only on checkin is most economical, but we can do nightlies as well, if that's useful. 

Comment 2

10 years ago
The basics of building Prism is documented here:

You should be able to use a XULRunner SDK, but you still need to checkout enough of the Mozilla build system for the build system to work. I usually just pull the "xulrunner" tree, but even pulling "l10n-checkout" should be enough.

The trunk source code can be checked out of Mozilla SVN from here:

Checkout the code into the "mozilla" folder, we typically pull the Prism trunk into "prism" subfolder.

We then use a mozconfig as described in the MDC article to start the build.

I can attach my mozconfig if it would be helpful
OS: Mac OS X → All
Priority: -- → P3
Hardware: PC → All
Component: Release Engineering → Release Engineering: Future
QA Contact: build → release
We need to complete our transition to nightlies on buildbot, and boost the number of slaves, before doing this.
Depends on: 401936
mfinkle: Is this still needed?
probably not. if it comes up again, we can reopen or file a new bug.
Last Resolved: 9 years ago
Resolution: --- → WONTFIX

Comment 6

9 years ago
If it is possible to set this up now, it would certainly be preferable to having me do all the release builds. Nightly builds would be useful as well, although not essential.

Comment 7

8 years ago
Moving closed Future bugs into Release Engineering in preparation for removing the Future component.
Component: Release Engineering: Future → Release Engineering


5 years ago
Product: → Release Engineering
You need to log in before you can comment on or make changes to this bug.