Now that things have mostly stabilized in master, we need to backport CI changes into the current release branches (at least 25.x & ideally 24.x) so that CI continues to run there. This may end up being a subset of CIs? This will likely also be useful for downstream/forks, i.e inquisition cc @ajtowns?
ci: backport relevant migration changes to current release branches #28416
issue fanquake opened this issue on September 5, 2023-
fanquake commented at 3:52 PM on September 5, 2023: member
- fanquake added the label Tests on Sep 5, 2023
-
maflcko commented at 4:03 PM on September 5, 2023: member
25.x should already have all relevant backports, see #27887, except maybe for the docker->podman replacement, which should be a single line diff, see #28410 (comment)
Looks like in 28410 the windows build failed for an unknown reason, so maybe the two GHA tasks can be backported?
-
fanquake commented at 4:21 PM on September 5, 2023: member
25.x should already have all relevant backports, see #27887,
Right, I'll look at some of those for 24.x.
except maybe for the docker->podman replacement, which should be a single line diff, see #28410 (comment)
This should also already be in 25.x https://github.com/bitcoin/bitcoin/blob/8825983716abbc4d9125c0ee44cf4a0a470a1a27/ci/test/04_install.sh#L43 unless there are further calls that need replacing?
so maybe the two GHA tasks can be backported?
I'll look at this.
-
fanquake commented at 4:04 PM on September 6, 2023: member
CI for 25.x, https://github.com/bitcoin/bitcoin/runs/16549476169, from the merge of #28047 looking decent.
-
maflcko commented at 2:31 PM on September 14, 2023: member
yeah, it is all-green, so I guess this can be closed, apart from cherry-picking the 25.x CI changes to 24.x, if needed?
-
fanquake commented at 2:41 PM on September 14, 2023: member
Yea, I might follow up with cherry-picking something to 24.x, but I also don't expect too much more activity for that branch.
- fanquake closed this on Sep 14, 2023
- bitcoin locked this on Sep 13, 2024
