mirror of
https://we.phorge.it/source/phorge.git
synced 2024-11-18 12:52:42 +01:00
7ad4c9c056
Summary: Ref T8095. Harbormaster has a `BuildItem` class, but it has no table and is unused. This was an earlier idea about representing lint/unit results and some other possible types of messages, but I think we want to be more specific than this. Remove `BuildItem` and add `Lint` and `Unit` storage. These tables roughly parallel how we store lint/unit messages today, with some guesses about how where they'll go in the future. Test Plan: Ran `bin/storage upgrade` and got a clean adjust out of it. Reviewers: btrahan Reviewed By: btrahan Subscribers: hach-que, epriestley Maniphest Tasks: T8095 Differential Revision: https://secure.phabricator.com/D13329
13 lines
621 B
SQL
13 lines
621 B
SQL
CREATE TABLE {$NAMESPACE}_harbormaster.harbormaster_buildunitmessage (
|
|
id INT UNSIGNED NOT NULL AUTO_INCREMENT PRIMARY KEY,
|
|
buildTargetPHID VARBINARY(64) NOT NULL,
|
|
engine VARCHAR(255) COLLATE {$COLLATE_TEXT} NOT NULL,
|
|
namespace VARCHAR(255) COLLATE {$COLLATE_TEXT} NOT NULL,
|
|
name VARCHAR(255) COLLATE {$COLLATE_TEXT} NOT NULL,
|
|
result VARCHAR(32) COLLATE {$COLLATE_TEXT} NOT NULL,
|
|
duration DOUBLE,
|
|
properties LONGTEXT COLLATE {$COLLATE_TEXT} NOT NULL,
|
|
dateCreated INT UNSIGNED NOT NULL,
|
|
dateModified INT UNSIGNED NOT NULL,
|
|
KEY `key_target` (buildTargetPHID)
|
|
) ENGINE=INNODB, COLLATE {$COLLATE_TEXT};
|