Closed Bug 425408 Opened 17 years ago Closed 16 years ago

move tinderboxpoller.py to buildbotcustom

Categories

(Release Engineering :: General, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: bhearsum, Unassigned)

Details

Attachments

(1 file)

This got commited to our tree before buildbotcustom existed, but I think it's time to move it out :).
Summary: move tinderboxboxpoller.py to buildbotcustom → move tinderboxpoller.py to buildbotcustom
a+, agreed.
Component: Release Engineering: Talos → Release Engineering: Future
QA Contact: build → release
Assignee: nobody → bhearsum
Priority: -- → P2
I don't think we should remove it from the Buildbot tree just yet -- since things are still using it. For now, let's copy it to buildbotcustom so we can use it from there in the future. We can leave this bug open and convert the existing masters when we get Talos using buildbotcustom.
Attachment #314941 - Flags: review?(rcampbell)
Attachment #314941 - Flags: review?(rcampbell) → review+
Comment on attachment 314941 [details] [diff] [review] [checked in] copy tinderboxpoller to buildbotcustom RCS file: /cvsroot/mozilla/tools/buildbotcustom/changes/tinderboxpoller.py,v done Checking in changes/tinderboxpoller.py; /cvsroot/mozilla/tools/buildbotcustom/changes/tinderboxpoller.py,v <-- tinderboxpoller.py initial revision: 1.1 done
Attachment #314941 - Attachment description: copy tinderboxpoller to buildbotcustom → [checked in] copy tinderboxpoller to buildbotcustom
We'll come back to this when we convert the Talos master(s) to buildbotcustom.
Assignee: bhearsum → nobody
Priority: P2 → P3
Adding Alice to the discussion. I see the file in http://hg.mozilla.org/build/buildbotcustom/file/tip/changes/tinderboxpoller.py Is there anything left to do in this bug? RESOLVED FIXED?
I don't believe that any talos master uses tinderboxpoller anymore. So wontfix.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WONTFIX
Moving closed Future bugs into Release Engineering in preparation for removing the Future component.
Component: Release Engineering: Future → Release Engineering
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: