Closed Bug 489483 Opened 15 years ago Closed 13 years ago

Add "periodic clobbers" steps to our buildbots

Categories

(SeaMonkey :: Release Engineering, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: sgautherie, Unassigned)

References

Details

Firefox and Thunderbird have these.

Bug 489336 comment 5:
{
From  Robert Kaiser   2009-04-21 08:25:41 PDT

[...] it dawned to me that we sometimes had problems with dep test builds [...]
Let me clobber the test machine to see if this helps.
}
In the same way as we are doing bug 494676,
do you know what SeaMonkey(-Ports) buildbot misses? (factory code to sync', config to update, ...)
Possibly because I have disabled clobberer at the moment. I don't care much for this right now, this is still targeted LATEr in my brain, there's a whole list of more pressing stuff, including release automation.
Blocks: 513943
Depends on: 555449
Component: Project Organization → Release Engineering
QA Contact: organization → release
Ftr, missing this feature is confusing wrt package(-compare) reports:
i.e., when I checked bug 563012 patch Av1, all Linux/MacOSX/Windows builders were reporting the same thing, except MacOSX dep builds :-/
Blocks: 563012
(In reply to comment #3)
> Ftr, missing this feature is confusing wrt package(-compare) reports

I would shout at you loudly if you would go clobbering all dep builds every time you want to check for inconsistencies of packaging!
Blocks: 598546
Summary: Add "periodic clobbers" steps to our buidbots → Add "periodic clobbers" steps to our buildbots
We now have periodic clobbers setup, but we more often hit our free-space-clobbers than this. It was added with the clobberer setup.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.