Closed Bug 1445641 Opened 7 years ago Closed 6 years ago

Record deployments in New Relic and Speedcurve

Categories

(developer.mozilla.org Graveyard :: General, enhancement, P1)

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

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: jwhitlock, Assigned: rjohnson)

References

Details

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

What problem would this feature solve? ====================================== New Relic can keep track of deployments, and alert when performance changes due to a deployment. This will help track unexpected performance changes Who has this problem? ===================== Staff contributors to MDN How do you know that the users identified above have this problem? ================================================================== In bug 1412891, adding Brotli had a large impact on performance, but we can't use New Relic tools to diagnose How are the users identified above solving this problem now? ============================================================ Remembering around when a feature was shipped. Using standu.ps. Do you have any suggestions for solving the problem? Please explain in detail. ============================================================================== Tell New Relic when a new deployment is released Is there anything else we should know? ====================================== This used to be done in SCL3, and could be done again in Jenkins: https://github.com/mozilla/kuma/blob/3fc83cd4842426df20e378f5bca735707dba0563/scripts/chief_deploy.py#L94-L113
Priority: -- → P1
Whiteboard: [specification][type:feature] → [specification][type:feature][in-triage][points:2]
Keywords: in-triage
Whiteboard: [specification][type:feature][in-triage][points:2] → [specification][type:feature][points:2]
Assignee: nobody → safwan.rahman15
Priority: P1 → P2
See Also: → 1464892
Assignee: safwan.rahman15 → jwhitlock
Status: NEW → ASSIGNED
Commits pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/a74cb55c923d91659e8a9fa582c08c6989d39b43 bug 1445641, bug 1464892: Add deployment recorder scripts/record_deployments.py takes the starting and ending commit hashes, and calls the APIs for New Relic and SpeedCurve to record a deployment. It gets the API keys and IDs from the environment, to avoid printing them on the command line when calling the scripts. https://github.com/mozilla/kuma/commit/686f79b515b944648b9082e436c13641e98099c0 Merge pull request #4824 from jwhitlock/deployments-1445641-1464892 bug 1445641, bug 1464892: Add deployment recorder
Priority: P2 → P1
The next phase of work is to automatically record deployments as part of the deployment process, and it makes sense to do this for SpeedCurve at the same time.
Summary: Record deployments in New Relic → Record deployments in New Relic and Speedcurve
Transferring to Ryan for the Jenkins leg of this task.
Assignee: jwhitlock → rjohnson
Commits pushed to master at https://github.com/mdn/kumascript https://github.com/mdn/kumascript/commit/090c87b5a932cea68667491854d75049d2f97ba0 bug 1445641, bug 1464892: enable deployment recording https://github.com/mdn/kumascript/commit/4ca918453e5dbaadeec783afb270fa60f81c43cf Merge pull request #753 from escattone/record-deployments-1445641-1464892 bug 1445641, bug 1464892: enable deployment recording
Commits pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/aba86e8164337b0496a95d1b52240a13a2a9c1a2 bug 1445641, bug 1464892: enable deployment recording https://github.com/mozilla/kuma/commit/ea9e1cba6b89102b75f9fae8b4efdc2c10dcbded Merge pull request #4902 from escattone/record-deployments-1445641-1464892 bug 1445641, bug 1464892: enable deployment recording
Commits pushed to master at https://github.com/mdn/kumascript https://github.com/mdn/kumascript/commit/31acf3cafd0ac1c986d8e2ace9e19b6013b72b65 bug 1445641, bug 1464892: fix recording of deployments https://github.com/mdn/kumascript/commit/2cbc208401925230554fd3c62318f5db84121796 Merge pull request #757 from escattone/fix-record-deployments-1445641-1464892 bug 1445641, bug 1464892: fix recording of deployments
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Commits pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/226fd491c26ff5e34f404c0132f3d273e6e7fd0c bug 1445641: Only Kuma deploys in SpeedCurve Only register Kuma deploys in SpeedCurve, since KumaScript deploys usually happen at the same time and aren't expected to have an immediate impact on performance. https://github.com/mozilla/kuma/commit/a70cbc2f0471dc231a11ad26e6f0d295767def4d Merge pull request #4992 from jwhitlock/speedcurve-no-ks-1445641 bug 1445641: Only Kuma deploys in SpeedCurve
Commits pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/e8ca9f627d515e6b45658b224f2ba9bdca1476a5 bug 1445641: Ignore SpeedCurve in-progress 403 SpeedCurve won't run a deploy if one is in progress. Detect as a non-quite-success, not-quite-failure. Also, make the code more Python-3 compatible by using response.text, which should be decoded to unicode automatically. https://github.com/mozilla/kuma/commit/9c99dd7943901761a5d2d88683a249656c8e8576 Merge pull request #4993 from jwhitlock/speedcurve-ignore-403-1445641 bug 1445641: Ignore SpeedCurve in-progress 403
See Also: → 1503916
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.