Build a Tree of commits (at least prep it) #4

Merged
Ghost merged 11 commits from tree_builder into main 2022-10-26 19:33:13 +02:00

11 Commits

Author SHA1 Message Date
Stephan Kulow
4dc7e972a2 Make use of db.cursor() in with blocks 2022-10-26 15:49:14 +02:00
Stephan Kulow
217bbcadb5 Run the formatter from make all 2022-10-26 14:57:08 +02:00
Stephan Kulow
1346223822 Reshuffle schema versions after rebase 2022-10-26 14:56:38 +02:00
Stephan Kulow
9dbf3b9094 Import all projects before checking files - otherwise we end with 0s 2022-10-26 14:56:38 +02:00
Stephan Kulow
d961c13614 Ignore commits after the merge 2022-10-26 14:56:38 +02:00
Stephan Kulow
2784171f75 Create fake revisions for every commit in the base of a linked package
This is a rather complex operation, but whenever a package changes in
Factory, the inherited package gets a shadow revision consisting of the
3-way merge. If this happens due to a request being accepted, this is
actually in most cases also commited by 'buildservice-autocommit',
so we're making sure this is always happening (and are actually
duplicating revisions in cases that we filter out later as empty
commits).

To differenciate the fake revisions from the real revisions, I add
a fraction part
2022-10-26 14:56:38 +02:00
Stephan Kulow
d17e60a608 Add another table to store linked_revs
We need to create fake revisions when packages were touched that are
linked themselves
2022-10-26 14:20:28 +02:00
Stephan Kulow
089b215f4c Build a revision tree 2022-10-26 14:16:22 +02:00
Stephan Kulow
bc74b6950b Implement a fileshash function for revision 2022-10-26 14:15:42 +02:00
Stephan Kulow
5bd790e915 Import the fixtures into the test database for queries 2022-10-26 14:15:41 +02:00
Stephan Kulow
ce3863e1b5 Add the capability to export the package data as test fixture 2022-10-26 14:13:24 +02:00