Closed Bug 400509 Opened 17 years ago Closed 17 years ago

MozillaExperimental fx-win32-tbox needs to be updated to use MozillaBuild or have --disable-installer in its mozconfig

Categories

(Release Engineering :: General, defect, P2)

Product:
Release Engineering
Component:
General
Platform:
x86
Windows Vista
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: robert.strong.bugs, Assigned: coop)

Details

It has gone red due to it not having the version of NSIS that comes with MozillaBuild.
http://tinderbox.mozilla.org/MozillaExperimental/
Probably need to clone the current win32 tbox for mrz's testing, or set up a new box from the current ref platform.
Assignee: nobody → build
Component: Build Config → Build & Release
Priority: -- → P3
Product: Firefox → mozilla.org
QA Contact: build.config → mozpreed
Version: Trunk → other
For the time being I added back the !ifdef in the uninstaller so MozillaExperimental should go green.
I'm trying to have consistent numbers with what I had weeks ago - is this a huge impact?  I should be totally done by mid week (just need to run full clobber builds a couple times).
A couple of weeks shouldn't be a problem.
Assignee: build → nobody
QA Contact: mozpreed → build
Assignee: nobody → ccooper
Priority: P3 → P2
These builds seem to have disappeared from tinderbox. Were they disabled on purpose? Were these only temporary testing builds to begin with?
Status: NEW → ASSIGNED
These were the ones I was testing with and testing is all over and the VMs have been destroyed.
OK, we'll keep the config hint in mind for the next time we need to publish from a non-MozillaBuild VM.
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.