Closed
Bug 1434280
Opened 7 years ago
Closed 7 years ago
please deploy balrog 2.46 to prod
Categories
(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)
Cloud Services
Operations: Deployment Requests - DEPRECATED
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Assigned: oremj)
References
Details
Balrog version 2.46 is ready to be pushed to prod. Please deploy the new Docker images (v2.46) for admin, public, and the agent.
We'd like the production push for this to happen around 11am pacific on Tuesday, January 30th.
This release requires a schema change that needs to be done _prior_ to the new code going out. It can be performed by running the Docker image with the "upgrade-db" command, with DBURI set.
If anything goes wrong with the new version in production, we can safely rollback.
If anything goes wrong with just one of the apps, all of them must be rolled back.
Reporter | ||
Comment 1•7 years ago
|
||
We had some hiccups yesterday - largely centered around the fact that the original Docker build jobs in Taskcluster had to be retried (it looks like the deployment automation doesn't handle that) - but we got this done.
Thanks Jeremy!
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•