Closed
Bug 1177880
Opened 9 years ago
Closed 9 years ago
splice 1.1.22 deployment to production
Categories
(Content Services Graveyard :: Tiles: Ops, defect)
Content Services Graveyard
Tiles: Ops
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: kthiessen, Assigned: relud)
References
()
Details
+++ This bug was initially created as a clone of Bug #1176648 +++ splice 1.1.22 adds the ability to track tiles per channel, and adds a new channel (and consequent tile index upload in S3). Contains a migration that adds a new column, and a new entry in the channels table, and does some very light data migration (which are only applicable to production): https://github.com/mozilla/splice/blob/1.1.22/ddl/migrations/redshift/1433974555.sql This is prompted by the need to deploy a different set of tiles to firefox pre-release users as to release users. 1.1.19 is currently deployed in production. Here are the changes from CHANGELOG.md since then: > 1.1.21 > ====== > > * fix cache key to include channel id in distribution.js > > 1.1.20 > ====== > > * Bug 1171116 - Add Firefox prerelease channel and add tracking per channel > > __note__: > * includes schema change/migration > * ddl/migrations/redshift/1433974555.sql > > 1.1.19 > ====== > > * Make time limits JS regex friendly (json-schema)
Reporter | ||
Updated•9 years ago
|
Summary: splice 1.1.22 deployment to staging → splice 1.1.22 deployment to production
Assignee | ||
Comment 1•9 years ago
|
||
The db migration for this has been executed, but splice has failed to deploy twice due to unavailable yum repos. It looks like the problem is fixed now, so I'm going to attempt to deploy one more time.
Assignee | ||
Comment 2•9 years ago
|
||
Deploy succeeded in prod.
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
•