ci: enable systemd repo build testing
With this change, the build test will only build changed aports when they are in an enabled repo. It will also detect when a changed aport is in extra-repos/systemd, and build it later with systemd support enabled.
This is meant to replace a similar patch in the systemd staging repo: ab46a0a7
Merge request reports
Activity
mentioned in merge request !5563 (merged)
By clayton craft on 2024-09-09T22:32:02
added 1 commit
- 633b363c - ci: lib: enable systemd if changed pkgs are in systemd repo
By clayton craft on 2024-09-09T22:46:57
- Resolved by Administrator
added 1 commit
- 035d4460 - ci: enable systemd repo build testing
By clayton craft on 2024-09-10T22:29:25
- Resolved by Administrator
- Resolved by Administrator
added 1 commit
- d932f7a3 - ci: enable systemd repo build testing
By clayton craft on 2024-09-10T22:54:16
- Resolved by Administrator
Thanks for making this!
I wonder if this is the right approach, with adding -systemd jobs for each variant...
Correct me if I'm wrong, but I think instead we need to do the following:
- in the same
build-$arch
job:- build all non-systemd packages that have been changed first
- afterwards, if there are any packages that were changed in
extra-repos/systemd
:- set systemd to always enabled
- build these packages
This is how bpo would build it too, and this way we don't build a lot of packages twice. linux packages are already excluded, but this would still build everything else twice in the current form, such as cross compilers, firmware, device packages, etc.
By Oliver Smith on 2024-09-11T23:32:47
Edited by Ghost User - in the same
added 1 commit
- 96f887b1 - ci: build_changed_aports: fix building changed aports in extra-repos/systemd
By clayton craft on 2024-09-11T17:33:30
added 1 commit
- 2fe596a2 - ci: build_changed_aports: fix building changed aports in extra-repos/systemd
By clayton craft on 2024-09-11T17:34:16