ci: force build of new/updates recipes #797
Conversation
ndechesne
requested review from
vkraleti,
ricardosalveti and
sbanerjee-quic
as code owners
|
wait wait.. this needs more testing/thoughts before we merge! e.g. if we try to build linux-qcom-staging (assuming a PR changes that file), we get: ERROR: Nothing PROVIDES 'linux-qcom-staging' |
Test jobs for commit 1985c79 |
In a PR test build, it's possible to have a new recipe (or updates with a bbappend) which is not included in any image we build. We could do a 'world' build but that would be really expensive. Instead this change tries to catch any updated .bb or .bbappend file, and force a bitbake build. If the recipe was already built as part of the image, it should be a quick no-op. If the recipe was not built, then it's a good thing to check that it builds! Signed-off-by: Nicolas Dechesne <[email protected]>
Test jobs for commit c5fd362 |
Yeah, recipes depending on provides won't work that easily. How is this managed with world? |
world is not a recipe/target. it's intercepted by bitbake and it uses the internal recipe/data store. it would be nice to have a 'world' target that only builds everything from a layer instead.. i am not sure how difficult that would be.. |
If this was purely for populating sstate-cache, I'd suggest using |
Currently we also need to filter boot images and some other packages. If I have time, I will take a look at reworking those recipes to remove possible conflicts. |
Having boot firmware as machine-spefic recipes complicates testing (as one would have to filter those from CI builds lke #797) and prevents building rescue images with generic machine configs. Rework boot firmware, partiion configuration and qcomflash recipes in order to make that code work with any machine. Closes #713
|
This pull request has been marked as stale due to 30 days of inactivity. To prevent automatic closure in 5 days, remove the stale label or add a comment. You can reopen a closed pull request at any time. |
In a PR test build, it's possible to have a new recipe (or updates with a bbappend) which is not included in any image we build. We could do a 'world' build but that would be really expensive. Instead this change tries to catch any updated .bb or .bbappend file, and force a bitbake build.
If the recipe was already built as part of the image, it should be a quick no-op. If the recipe was not built, then it's a good thing to check that it builds!