phorge-phorge/resources/sql/autopatches/20210713.harborcommand.02.drop.sql at e8ea7a4a3697db4d0d8d36edfce57d0f06c6fd15 - revi-archive/phorge-phorge - SiliconForest Atelier

revi-archive/phorge-phorge

mirror of https://we.phorge.it/source/phorge.git synced 2024-11-14 19:02:41 +01:00

epriestley b48d4fabaf Merge the "HarbormasterBuildCommand" table into "HarbormasterBuildMessage"

Summary:
Ref T13072. These two similar tables don't make sense to keep separate. Instead, make Build a valid receiver for BuildMessage objects.

These tables are practically the same, so this is straightforward: just copy the rows in and then drop the old table.

(This table was trivial and ephemeral anyway, so I'm not bothering to do the usual "keep it around for a couple years just in case".)

Test Plan:
  - Populated BuildCommand table, ran migration, saw Builds end up in the proper transitional state (e.g., pausing, aborting, restarting) with appropriate queued messages.
  - Queued new messages by clicking UI buttons.
  - Ran BuildWorkers, saw them process messages and mark them as consumed.

Subscribers: PHID-OPKG-gm6ozazyms6q6i22gyam

Maniphest Tasks: T13072

Differential Revision: https://secure.phabricator.com/D21684

2021-07-21 14:16:53 -07:00

1 line

74 B

SQL

Raw Blame History

DROP TABLE IF EXISTS {$NAMESPACE}_harbormaster.harbormaster_buildcommand;