Commit d7e6add
committed
ci: fetch legacy repo history so pre-migration sync SHAs resolve
Packages synced to OBS before the migration from
rjd15372/percona-obs-packaging to percona/obs-packaging carry sync
comments like 'sync: main@6f95b5a (rjd15372/...)' whose SHAs come from the
legacy repo's rebased history and do not exist in a percona-only clone.
The branch-decision/skip fast path runs git log <sha>..HEAD per package, so
an unresolvable SHA conservatively falls through to the full content check:
every PR run re-ran services for essentially the whole tree (~10 min), and
it also exposed the vendor.tar.gz drift promotions on PR #5.
The two histories share ancestry up to the migration point, so simply
fetching the legacy refs makes the old SHAs resolvable and the range
queries correct: verified in a percona-only clone that after the fetch
6f95b5a..HEAD is empty for untouched packages (fast aggregate) and still
lists the PR commits for packages the PR really changed.
The fetch is fail-open (warning only) and should be dropped once all
packages have been re-synced with percona/obs-packaging SHAs in their
comments.
Signed-off-by: Ricardo Dias <ricardo.dias@percona.com>1 parent 864cd6a commit d7e6add
2 files changed
Lines changed: 24 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
120 | 120 | | |
121 | 121 | | |
122 | 122 | | |
| 123 | + | |
| 124 | + | |
| 125 | + | |
| 126 | + | |
| 127 | + | |
| 128 | + | |
| 129 | + | |
| 130 | + | |
| 131 | + | |
| 132 | + | |
| 133 | + | |
| 134 | + | |
123 | 135 | | |
124 | 136 | | |
125 | 137 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
42 | 42 | | |
43 | 43 | | |
44 | 44 | | |
| 45 | + | |
| 46 | + | |
| 47 | + | |
| 48 | + | |
| 49 | + | |
| 50 | + | |
| 51 | + | |
| 52 | + | |
| 53 | + | |
| 54 | + | |
| 55 | + | |
| 56 | + | |
45 | 57 | | |
46 | 58 | | |
47 | 59 | | |
| |||
0 commit comments