Closed
Bug 1395750
Opened 7 years ago
Closed 7 years ago
In Jenkins, for both kuma and kumascript, generate revision hash and store in Docker image (for AWS)
Categories
(developer.mozilla.org Graveyard :: General, enhancement)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rjohnson, Assigned: rjohnson)
Details
(Keywords: in-triage, Whiteboard: [specification][type:feature])
What problem would this feature solve? ====================================== It generates the revision hash and associates it with its Docker image, providing the foundation for serving the hash from Django in the AWS realm. Who has this problem? ===================== All visitors to MDN How do you know that the users identified above have this problem? ================================================================== N/A How are the users identified above solving this problem now? ============================================================ In SCL3, the revision hash is generated in the deployment script (scripts/chief_deploy.py) and served via Django from the media root (https://developer.mozilla.org/media/revision.txt) Do you have any suggestions for solving the problem? Please explain in detail. ============================================================================== See title. Is there anything else we should know? ====================================== No.
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → rjohnson
Comment 1•7 years ago
|
||
Fixed as part of bug 1395684
Updated•4 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
•