Closed
Bug 1291464
Opened 9 years ago
Closed 9 years ago
seta broke because headers were changed for production data without notice
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Infrastructure & Operations Graveyard
CIDuty
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: kmoir, Assigned: kmoir)
Details
Attachments
(1 file)
2.07 KB,
patch
|
kmoir
:
checked-in+
|
Details | Diff | Splinter Review |
No description provided.
Assignee | ||
Comment 1•9 years ago
|
||
this is a temp fix so we can reconfig and run releases
as an aside, since fennec for linux has been removed on bb for debug only, we have to refactor the script to account for this since it assumes seta applies to both debug and opt
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → kmoir
Assignee | ||
Comment 2•9 years ago
|
||
Joel can we get a heads up on these changes so this doesn't happen again? We just parse the content of an url like this and map them to buildbot config platforms http://alertmanager.allizom.org/data/setadetails/?date=2016-08-02&buildbot=1&branch=fx-team&inactive=1
Flags: needinfo?(jmaher)
Assignee | ||
Comment 3•9 years ago
|
||
See that we should have a staging env in the new heroku setup - yay!
https://bugzilla.mozilla.org/show_bug.cgi?id=1286358#c6
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(jmaher)
Resolution: --- → FIXED
Assignee | ||
Updated•9 years ago
|
Attachment #8777108 -
Flags: checked-in+
Comment 4•9 years ago
|
||
sorry :kmoir for not replying earlier- I was out part of this week and I honestly needed to figure out what the difference was and what to do. Either way, we are much closer to a production/staging environment- apologies for the confusion
Updated•7 years ago
|
Component: Platform Support → Buildduty
Product: Release Engineering → Infrastructure & Operations
Updated•5 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•