Closed Bug 468264 Opened 17 years ago Closed 16 years ago

SeaMonkey-Ports has not any build since 2008/09/27 06:09:13

Categories

(SeaMonkey :: Release Engineering, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: sgautherie, Unassigned)

References

()

Details

What's the bug here?
I'd think that the bug which calls for a report in bmo is "the descriptions of boxes on the top of the SM-Ports tree are out of date, since unless Sun plans on bringing nba back, there are no boxes to describe."
I have killed the boxes I know about from that top message: My boxes can't build trunk any more because parallel tinderbox and buildbot setups don't work in a way that they're doing serial builds, and they need to do 1.1.x builds on tinderbox, while tinderbox doesn't support hg-based builds, we can only reasonably use buildbot there. Additionally, we have decent trunk boxes anyway. The hg test thing was made the official stuff on the main waterfall when we moved over to hg. Kai, what's up with s15277822/kuix? Still an intention of running SeaMonkey builds there?
(In reply to comment #2) > "the descriptions of > boxes on the top of the SM-Ports tree are out of date, since unless Sun plans > on bringing nba back, there are no boxes to describe." Yes, I'd be perfectly happy with either getting the boxes back online, or unlisting them if they were retired on purpose. Even retiring the page itself, if no build applies anymore. (In reply to comment #3) > My boxes can't build trunk any more [...] > Additionally, we have decent trunk boxes anyway. I fully agree with that :-)
Decent trunk-ish boxes: if someone had the hardware and the will, SM-Ports would be a handy place to get some comm-central+mozilla-central coverage, while we wait for actual official Tb boxes building it.
I expect gozer may be setting up build boxes fairly soon, so I wouldn't worry about c-c and m-c too much.
Assignee: build-config → nobody
QA Contact: build-config → build-config
There is no bug here, let's close this.
Status: NEW → RESOLVED
Closed: 16 years ago
Component: Build Config → Release Engineering
QA Contact: build-config → release
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.