Closed Bug 1464892 Opened 7 years ago Closed 7 years ago

Record deployments in Speedcurve

Categories

(developer.mozilla.org Graveyard :: Performance, enhancement, P2)

Product:
developer.mozilla.org Graveyard
Component:
Performance
Platform:
All
Other
Type:
enhancement

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1445641

People

(Reporter: jwhitlock, Assigned: jwhitlock)

References

Details

(Keywords: in-triage, Whiteboard: [specification][type:feature][points=3])

What problem would this feature solve? ====================================== We're using Speedcurve for synthetic monitoring (measuring timing information from known servers). It may be useful to record deployments, to see if there are performance changes around deployments Who has this problem? ===================== Staff contributors to MDN How do you know that the users identified above have this problem? ================================================================== We've hired a contractor for a performance audit who recommended this. How are the users identified above solving this problem now? ============================================================ Manually running Speedcurve tests Do you have any suggestions for solving the problem? Please explain in detail. ============================================================================== We can add a step in Jenkins to run a task to record a deployment in SpeedCurve once the Kubernetes deployment has rolled out. Is there anything else we should know? ====================================== The API key should be treated as sensitive, and not appear in plaintext. Kubernetes secrets would allow it to be loaded as needed into the environment.
See Also: → 1445641
Speedcurve documentation: https://api.speedcurve.com/#add-a-deploy
Assignee: nobody → jwhitlock
Status: NEW → ASSIGNED
Keywords: in-triage
Priority: -- → P2
Whiteboard: [specification][type:feature] → [specification][type:feature][points=3]
Tracking remaining work along with New Relic deployment tracking
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.