The current build process leaves copies of entire product-directory-trees on different machines throughout the release process, without any automated cleanup/recycling process in place. This causes us to run out of disk space on different machines, at different times and causes complicated manual restarts. Examples of this fallout are: bug#394757, bug#342972, bug#393565, bug#361548. Its unclear when we should: - keep a copy, because it would help us debug issues found after-the-fact - delete a copy, because its identical to what we have elsewhere (Setting up nagios monitoring to watch for this might be a good idea also)
11 years ago
Priority: -- → P3
Another example is: bug#395622
11 years ago
OS: Mac OS X → All
Hardware: PC → All
Assignee: build → nobody
QA Contact: mozpreed → build
I think we've got this in place with the new Makefile and syncing to externalStaging (in the staging environment). John/Rob, what do you guys think?
(In reply to comment #2) > I think we've got this in place with the new Makefile and syncing to > externalStaging (in the staging environment). > > John/Rob, what do you guys think? I think this bug is not specific enough, given the examples in comment 0. I suggest we mark this INVALID or WONTFIX AND file more specific bugs.
As best I can tell, everything that matters here has a bug.
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → INVALID
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.