Closed
Bug 1341331
Opened 7 years ago
Closed 2 years ago
[shipit-v2] balrog service
Categories
(Release Engineering :: Applications: Shipit, defect, P2)
Release Engineering
Applications: Shipit
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: jlund, Unassigned)
References
Details
normally we have taskcluster handle balrog communication for releases. however, this service may be useful for handling requests outside releases like: * whats new pages * setting update rate * global shut off we could also plug these endpoints into a pipeline graph if the requirements are known ahead of time.
Updated•7 years ago
|
Priority: -- → P2
Assignee | ||
Updated•2 years ago
|
Component: Applications: ShipIt (backend) → Applications: ShipIt
Comment 1•2 years ago
|
||
Currently we use balrogscript, and I don't know of any plans to change that.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•