Closed
Bug 478683
Opened 15 years ago
Closed 15 years ago
clobberer doesn't make its purpose clear
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jruderman, Assigned: catlee)
Details
Attachments
(1 file)
575 bytes,
patch
|
bhearsum
:
review+
catlee
:
checked-in+
|
Details | Diff | Splinter Review |
http://tinderbox.mozilla.org/showbuilds.cgi?tree=Firefox&norules=1 says "Use the clobberer if a build needs to be clobbered." and links to https://build.mozilla.org/clobberer/, which has no instructions. 1) What does it mean to "clobber" something? Does it cause it to do another build right away, or does it just ensure that next time it builds, it throws away old intermediate files? 2) When is it appropriate to "clobber" rather than "kick" or file an IT bug? 3) When should I use this web tool instead of the "CLOBBER file" technique?
Assignee | ||
Updated•15 years ago
|
Assignee: nobody → catlee
Reporter | ||
Comment 1•15 years ago
|
||
http://atlee.ca/blog/2009/02/09/clobbering-the-trees/ explains it better than the current text on Tinderbox.
Reporter | ||
Comment 2•15 years ago
|
||
Maybe the documentation should live at https://wiki.mozilla.org/Build:ClobberingATinderbox, with the clobberer just linking to this wiki page.
Assignee | ||
Comment 3•15 years ago
|
||
Attachment #371847 -
Flags: review?(bhearsum)
Updated•15 years ago
|
Attachment #371847 -
Flags: review?(bhearsum) → review+
Assignee | ||
Comment 4•15 years ago
|
||
Comment on attachment 371847 [details] [diff] [review] Add links to wiki changeset: 261:d4b2a8b50ca1
Attachment #371847 -
Flags: checked‑in+ checked‑in+
Assignee | ||
Updated•15 years ago
|
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•