Closed
Bug 1350014
Opened 9 years ago
Closed 8 years ago
Enable a "What's Deployed" for KumaScript
Categories
(developer.mozilla.org Graveyard :: KumaScript, enhancement)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jwhitlock, Unassigned)
Details
(Keywords: in-triage, Whiteboard: [specification][type:feature])
What problem would this feature solve?
======================================
It is challenging to determine what KumaScript macros are deployed to production, and what are pending deployment
Who has this problem?
=====================
Core contributors to MDN
How do you know that the users identified above have this problem?
==================================================================
Contributors ask how long it takes for their merged changes to become live, such as this thread:
https://groups.google.com/forum/#!topic/mozilla.dev.mdn/AJiqQ3AQz_I
How are the users identified above solving this problem now?
============================================================
You can see what Kuma version is deployed on MDN. because a file "revision.txt" includes the deployed commit hash:
https://whatsdeployed.io/?owner=mozilla&repo=kuma&name[]=Stage&url[]=https://developer.allizom.org/media/revision.txt&name[]=Prod&url[]=https://developer.mozilla.org/media/revision.txt
You can load the deployed commit in GitHub:
https://github.com/mozilla/kuma/commit/106cffbb01a52f28860e62b0408f304c86bfe68c
Then "Browse Files" to see all the files at that commit:
https://github.com/mozilla/kuma/tree/106cffbb01a52f28860e62b0408f304c86bfe68c
And then the KumaScript submodule checkout:
https://github.com/mozilla/kumascript/tree/2e455deee647076c95016547598d2f4d73dea6dd
You can then view the KumaScript repository history, to see what later commits are not included:
https://github.com/mozilla/kumascript/commits/master
Do you have any suggestions for solving the problem? Please explain in detail.
==============================================================================
If the deployment included writing the KumaScript revision to a file (such as kumascript-revision.txt), then the "What's Deployed" tool could be used to view what is deployed and what commits are pending. This change would be in chief_deploy.py:
https://github.com/mozilla/kuma/blob/master/scripts/chief_deploy.py#L107-L115
Is there anything else we should know?
======================================
Idea was brought up by shobson in a work week meeting about reviewing KumaScript PRs.
Comment 1•9 years ago
|
||
Commits pushed to master at https://github.com/mozilla/kuma
https://github.com/mozilla/kuma/commit/bb715317f26774180b3432f792fe25efa83fa1a1
bug 1350014: Remove unused prime_app deploy task
https://github.com/mozilla/kuma/commit/699a29aeffaf5afc475d025454446cfed5338e8d
bug 1350014: Record KumaScript revision on deploy
https://github.com/mozilla/kuma/commit/e9707cf09119a282cb12d07012754587b591f85b
Merge pull request #4165 from jwhitlock/kumascript-deployed-1350014
bug 1350014: Record KumaScript revision on deployment
| Reporter | ||
Comment 2•8 years ago
|
||
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•