1337379 - please deploy balrog 2.20.1 to stage/prod

Status: RESOLVED FIXED

(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)

Description

[[e-mail] (:bhearsum)]

Balrog version 2.20 is ready to be pushed to stage. Please deploy the new Docker image (master-2017-02-07-15-00) the admin and public webapps, and the new Docker image for the Agent (master-2017-02-07-15-00).

We'd like the production push for this to happen sometime between 11am and 1pm pacific on Wednesday, February 8.

This push requires a schema change that needs to be done _prior_ to the new code going out. That can be performed by running the Docker image with the "upgrade-db" command, with DBURI set. This schema change is a simple alter to a few existing columns - no new tables!

Comment 1

[[e-mail] (:bhearsum)]

(In reply to Ben Hearsum (:bhearsum) from comment #0)
> This push requires a schema change that needs to be done _prior_ to the new
> code going out. That can be performed by running the Docker image with the
> "upgrade-db" command, with DBURI set. This schema change is a simple alter
> to a few existing columns - no new tables!

We'll be widening the "version" column on the rules, rules_history, rules_scheduled_changes, and rules_scheduled_changes_history columns from 10 characters to 75. This is part of bug 1257298.

Comment 2

[Benson Wong [:mostlygeek]]

Database schema change was successful on stage.

Comment 3

[[e-mail] (:bhearsum)]

Everything looks good in stage, but we had a last minute bug discovered that I'd like to get in this push if possible. Can we update admin/public to master-2017-02-08-15-06?

Comment 4

[[e-mail] (:bhearsum)]

(In reply to Ben Hearsum (:bhearsum) from comment #3)
> Everything looks good in stage, but we had a last minute bug discovered that
> I'd like to get in this push if possible. Can we update admin/public to
> master-2017-02-08-15-06?

This happened, and looks good in stage.

Comment 5

[Benson Wong [:mostlygeek]]

deployed to production.