Closed
Bug 1310303
Opened 8 years ago
Closed 8 years ago
teach the Balrog agent how to determine whether or not scheduled changes meet signoff requirements
Categories
(Release Engineering Graveyard :: Applications: Balrog (backend), defect, P1)
Release Engineering Graveyard
Applications: Balrog (backend)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Assigned: vjoshi)
References
Details
(Whiteboard: [lang=python])
No description provided.
Reporter | ||
Updated•8 years ago
|
Priority: -- → P1
Whiteboard: [lang=python]
Assignee | ||
Updated•8 years ago
|
Assignee: nobody → varunj.1011
Reporter | ||
Comment 1•8 years ago
|
||
Varun, my "rs-apis" branch now returns "required_signoffs" as part of each Scheduled Change, which should unblock you here. Do you think you'll be able to have a look at this soon?
Flags: needinfo?(varunj.1011)
Assignee | ||
Comment 2•8 years ago
|
||
Sorry for the delay with the reply! I will look into this today and tomorrow.
Flags: needinfo?(varunj.1011)
Comment 3•8 years ago
|
||
Commit pushed to master at https://github.com/mozilla/balrog
https://github.com/mozilla/balrog/commit/dc79a6b06ae1f38fd2d3fb20d8df20e5a7481d35
Bug 1310303 - teach the Balrog agent how to determine whether or not scheduled changes meet signoff requirements (#252). r=bhearsum
Reporter | ||
Comment 4•8 years ago
|
||
In production. Thanks for your hard work on this Varun!
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Updated•5 years ago
|
Product: Release Engineering → Release Engineering Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•