Closed Bug 1002627 Opened 9 years ago Closed 9 years ago

add required config for balrog to release/esr release configs

Categories

(Release Engineering :: Release Automation: Other, defect)

Product:
Release Engineering
Component:
Release Automation: Other
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: bhearsum, Assigned: bhearsum)

Details

Attachments

(1 file)

add required balrog stuff for esr/release
3.85 KB, patch
nthomas
: review+
bhearsum
: checked-in+
Details | Diff | Splinter Review 
Required item missing in config: testChannels
Required item missing in config: releaseChannel
Required item missing in config: testChannelRuleIds

We'll want to re-use the same test channels as the beta channel right now, until bug 986990 is fixed.
Turns out I didn't do this for staging either!
Assignee: nobody → bhearsum
Status: NEW → ASSIGNED
Attachment #8413963 - Flags: review?(nthomas)
Summary: balrog submitter failed for 29.0 → add required config for balrog to release/esr release configs
What's the idea with the releasetest ruleID being shared for release+beta+esr ? Just not care until we resolve that issue ? Otherwise this looks fine.
(In reply to Nick Thomas [:nthomas] (PTO Apr 17-27 PST) from comment #2)
> What's the idea with the releasetest ruleID being shared for
> release+beta+esr ? Just not care until we resolve that issue ? Otherwise
> this looks fine.

Yep. I'm just emulating the current behaviour on AUS2/3. We can migrate to better and non-overlapping channel names in bug 986990.
Attachment #8413963 - Flags: review?(nthomas) → review+
Attachment #8413963 - Flags: checked-in+
Should be fixed for the next RC.
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.