Colin Watson has proposed merging ~cjwatson/launchpad:db-revision-status-report-das into launchpad:db-devel.
Commit message: Add RevisionStatusReport.distro_arch_series Requested reviews: William Grant (wgrant): db Launchpad code reviewers (launchpad-reviewers): db For more details, see: https://code.launchpad.net/~cjwatson/launchpad/+git/launchpad/+merge/448900 An awkward legacy of the order in which revision statuses and CI builds were designed is that revision status reports linked to a CI build don't record the series and architecture used for each individual CI build job. This is a problem when we need to be able to do things like filter the artifacts produced by a CI build to select only those built on a particular series, and in general it seems like information that would be worth tracking in the database. Add a column for it. -- Your team Launchpad code reviewers is requested to review the proposed merge of ~cjwatson/launchpad:db-revision-status-report-das into launchpad:db-devel.
diff --git a/database/schema/patch-2211-21-0.sql b/database/schema/patch-2211-21-0.sql new file mode 100644 index 0000000..fcc04d8 --- /dev/null +++ b/database/schema/patch-2211-21-0.sql @@ -0,0 +1,11 @@ +-- Copyright 2023 Canonical Ltd. This software is licensed under the +-- GNU Affero General Public License version 3 (see the file LICENSE). + +SET client_min_messages=ERROR; + +ALTER TABLE RevisionStatusReport + ADD COLUMN distro_arch_series integer REFERENCES distroarchseries; + +COMMENT ON COLUMN RevisionStatusReport.distro_arch_series IS 'The series and architecture for the CI build job that produced this report.'; + +INSERT INTO LaunchpadDatabaseRevision VALUES (2211, 21, 0);
_______________________________________________ Mailing list: https://launchpad.net/~launchpad-reviewers Post to : launchpad-reviewers@lists.launchpad.net Unsubscribe : https://launchpad.net/~launchpad-reviewers More help : https://help.launchpad.net/ListHelp