Closed Bug 432237 Opened 17 years ago Closed 17 years ago

Separate mozilla-central and actionmonkey in tinderbox

Categories

(Release Engineering :: General, defect, P3)

x86
Linux
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: benjamin, Assigned: bhearsum)

References

()

Details

Attachments

(2 files, 1 obsolete file)

We currently have a single "Mozilla2" tinderbox with both actionmonkey and mozilla-central builds. This is going to be unworkable. Instead, I think we should create separate tinderbox pages for "mozilla-central" and "actionmonkey" and send the build results to each page individually. This also means we can send the actionmonkey talos results directly to the actionmonkey waterfall, even though they aren't officially in production, without worrying about them being red or orange and causing "mozilla2" to shut down.
Alternately, we probably should consider moving everything that currently reports to "Firefox" and have it report to "Firefox-3.0.x" and have the mozilla-central stuff report to "Firefox". Thoughts?
Priority: -- → P3
If we were following existing convention, the current "Firefox" tinderbox would wind up as Mozilla1.9, although I guess the Firefox tinderbox changed convention anyway, so Firefox3.0 would probably be fine.
(In reply to comment #3) > If we were following existing convention, the current "Firefox" tinderbox would > wind up as Mozilla1.9, I'd be in favor of Mozilla1.9, as it fits with the existing Mozilla1.8.0, Mozilla1.8 and Mozilla2. What if we leave mozilla-central on the existing Mozilla2 tinderbox, and then have other mercurial branches show up on tinderbox called Mozilla2actionmonkey, Mozilla2projectfoo, Mozilla2projectbar, etc? although I guess the Firefox tinderbox changed > convention anyway, so Firefox3.0 would probably be fine. >
why "Mozilla2actionmonkey" instead of just "actionmonkey"? Sounds verbose. Mozilla 2 is just a version number, I'd hate to get caught up on it... what happens if actionmonkey gets bumped to mozilla 2.1?
(In reply to comment #5) > why "Mozilla2actionmonkey" instead of just "actionmonkey"? Sounds verbose. > Mozilla 2 is just a version number, I'd hate to get caught up on it... what > happens if actionmonkey gets bumped to mozilla 2.1? Yeah, "actionmonkey" is an equally fine name, imho. I was mostly concerned about using tinderboxen called Mozilla1.9 (for Firefox3.0) and Mozilla2 (for mozilla-central), as this felt consistent with how we've named tinderboxen for previous branches. (Obviously, all just my opinion, not trying to bikeshed this!)
I'm going to go ahead and create Actionmonkey - there seems to be agreement on that name. I'll leave the mozilla-central machines on Mozilla2 until we decide what to do there.
Assignee: nobody → bhearsum
Status: NEW → ASSIGNED
Attachment #320540 - Flags: review?(rcampbell)
Attachment #320538 - Flags: review?(rcampbell) → review+
Attachment #320540 - Flags: review?(rcampbell) → review+
Comment on attachment 320538 [details] [diff] [review] [checked in] move dep/nightly actionmonkey Applied in 8b9ebb53c0e7
Attachment #320538 - Attachment description: move dep/nightly actionmonkey → [checked in] move dep/nightly actionmonkey
Alright, future builds ("dep" and "nightly" class) of Actionmonkey should be reporting to the 'Actionmonkey' tinderbox now. I'll let Alice deal with the Talos ones.
Comment on attachment 320540 [details] [diff] [review] move actionmonkey talos to Actionmonkey tree >+c['status'].append(TinderboxMailNotifier( >+ fromaddr="rcampbell@mozilla.com", >+ tree="Mozilla2", ^ Should't that be Actionmonkey?
Attachment #320619 - Flags: review?(bhearsum) → review+
Attachment #320540 - Attachment is obsolete: true
Move talos actionmonkey testers to the Actionmonkey waterfall. Checking in master.cfg; /cvsroot/mozilla/tools/buildbot-configs/testing/talos/perfmaster/master.cfg,v <-- master.cfg new revision: 1.57; previous revision: 1.56 done
Now that talos is shifted is there anything else to do here?
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.

Attachment

General

Created:
Updated:
Size: