Closed
Bug 1210053
Opened 9 years ago
Closed 9 years ago
Create automation for the initial deployment of remote newtab pages
Categories
(Firefox :: New Tab Page, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: oyiptong, Unassigned)
References
Details
We are going to first deploy the newtab page in the Content Services AWS IAM. This tracks the automation that needs to be built for the deployment in this IAM's S3 bucket. The services team will be provided hostnames to point a CNAME to from this IAM.
Reporter | ||
Comment 1•9 years ago
|
||
To be clear, this bug includes the automation for: * the l10n build of the static files * deployment to s3 The CNAME setting will not be tracked in this bug
Reporter | ||
Comment 2•9 years ago
|
||
The initial static pages won't have any localization and will have a lot of duplication. The final build is tracked in bug 1186121
Reporter | ||
Comment 3•9 years ago
|
||
Example deployed page: https://newtab.cdn.mozilla.net/v0/aurora/en-US/index.html
Reporter | ||
Comment 4•9 years ago
|
||
all 16224 files for the initial landing are deployed
Reporter | ||
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•