Closed Bug 827367 Opened 12 years ago Closed 9 years ago

Ensure that all production slaves that can post to the graph server can be found on the graph server (or the graphs repo)

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task, P3)

Product:
Infrastructure & Operations Graveyard
Component:
CIDuty
Platform:
x86
macOS
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: armenzg, Unassigned)

References

Details

This would prevent the ever repeating human failure to add slaves to the graph server. jmaher, does datazilla needs these insertions as the graph server does? or should we wait until datazilla comes into production?
datazilla doesn't need pre defined information. It will be a few months before we are truly live, probably the end of the year before all branches are only reporting to datazilla.
Product: mozilla.org → Release Engineering
Changing the summary to not prescribe a solution. I think this works better at a pre-flight task per slave anyway.
Depends on: 712206
Priority: -- → P3
Summary: Add test to preproduction to ensure that all production slaves that can post to the graph server can be found on the graph server (or the graphs repo) → Ensure that all production slaves that can post to the graph server can be found on the graph server (or the graphs repo)
Where are we with datazilla after a year? Strongly tempted to WONTFIX this if I can and stop any manual muckery with graph server.
Datazilla isn't very close to deploying- we need to resolve the alerts before we can switch- as it stands Datazilla is a useful tool for investigating regressions- just a priority 2
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Component: Platform Support → Buildduty
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.