Closed Bug 1441203 Opened 6 years ago Closed 1 year ago

Simplify bouncer-check configs in mozharness

Categories

(Release Engineering :: Release Automation: Bouncer, enhancement)

Product:
Release Engineering
Component:
Release Automation: Bouncer
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: jlorenzo, Unassigned)

References

Details

After bug 1433459 lands, we shouldn't need them anymore in central. Then, we can let this ride the trains.
This should still live for Thunderbird, until it moves to bouncerscript.
Summary: Delete mozharness bouncer config → Delete mozharness bouncer config after Thunderbird moved to bouncerscript
@tomprince: I think we can close this, right?
Component: Release Automation: Other → Release Automation: Bouncer
Flags: needinfo?(mozilla)
I don't think so. Thunderbird is using bouncerscript now, so the prerequisite is satisfied now. I'm not sure the specific configs being referenced, though my guess would be the ones being used by bouncer-check? In that case, they can probably be simplified and/or moved to taskcluster/ci, rather than deleted.
Flags: needinfo?(mozilla)
Summary: Delete mozharness bouncer config after Thunderbird moved to bouncerscript → Simplify bouncer-check configs in mozharness

Bug 1737999 did some simplification, I don't think there's much more to do here.

Status: NEW → RESOLVED
Closed: 1 year ago
Depends on: 1737999
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.