Closed
Bug 1123745
Opened 11 years ago
Closed 9 years ago
Create What's Deployed site for One and Done
Categories
(Mozilla QA Graveyard :: One and Done, defect, P3)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: rbillings, Unassigned)
Details
Create a What's Deployed site for One and Done that shows the current status of bugs in development, staging, prod. Similar to what Reps has here:
https://whatsdeployed.paas.allizom.org/?owner=mozilla&repo=remo&name[]=Dev&url[]=https://reps-dev.allizom.org/static/revision.txt&name[]=Stage&url[]=https://reps.allizom.org/static/revision.txt&name[]=Prod&url[]=https://reps.mozilla.org/static/revision.txt
Comment 1•11 years ago
|
||
It looks like all we need to do for this is provide a file for each site that contains the sha of the latest github commit. For remo, the file is called revision.txt and lives in /static/revision.txt.
Ideally we would not have to update this file manually each time we deployed, and I am sure there is a script or something we could use (possibly via a post-commit hook) that would update the file. We should check with Tasos to see what they are doing for remo.
assigned:tessyjoseph1992@gmail.com
| Reporter | ||
Comment 3•10 years ago
|
||
This is available for contributors to work on.
| Reporter | ||
Comment 4•9 years ago
|
||
Project is being retired.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Updated•7 years ago
|
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•