Date
1 - 4 of 4
RFC: Feedback on changes to the AGL CI
|
Hi all!
As the number our images grow, we also need to expand our coverage in what images we build beside 'agl-demo-platform'. In a first step, we enabled building these images for qemux86-64: - agl-image-graphical-html5 (aka the html5 'only' demo) - agl-demo-platform with agl-compositor enabled (aka the new compositor) Future candidates are the cluster image and the telematic image. Any other variants that should be considered ? This is now also a good time to change what boards get built. And I'd like to gather feedback on this: The proposal is to: - replace the rpi3 with the rpi4 - replace intel-corei7-64 with the combined 'qemux86-64' - remove the dra7xx-evm ('vayu') build ? This will free-up build-capacity. After that change we would run CI-builds for: - qemux86-64 (all variants: demo-platform, html5-only, agl-compositor) - R-Car m3ulcb(-nogfx) - R-Car h3ulcb(-nogfx) - qemuarm - qemuarm64 - rpi4 Any comments, suggestions or objections? Best regards, Jan-Simon ------ Jan-Simon Möller AGL Release Manager The Linux Foundation Visit us at: www.automotivegradelinux.org lists.automotivelinux.org www.linuxfoundation.org
|
|
|
|
Hi Jan-Simon,
toggle quoted messageShow quoted text
A comment on images: adding the minimal image and a core common image (without any demo stuff) for all platforms is mandatory IMO: we saw in the past that from time to time, the minimal image wouldn't build or boot. FYI, minimal images on master are currently broken for m3ulcb/h3ulcb (and probably icefish): they don't boot due to a missing dtb... The fix is easy and we're working on it but my point is that nobody ever detected such obvious error because people tend to overuse demo images, which is a non-sense for industrial projects. Best regards, --- Stephane Desneux - CTO - IoT.bzh stephane.desneux@iot.bzh - www.iot.bzh
On 05/03/2020 18:49, Jan Simon Moeller wrote:
Hi all!
|
|
|
|
Marc
Hi Jan-Simon
toggle quoted messageShow quoted text
With the introduction of the telematics build can we please add the BBE baseline as a build as the automotive module has a profile? We regularly build ourselves against each release and make sure the platform is supported. Kind Regards Marc e marc.murphy@sancloud.co.uk w www.sancloud.co.uk Follow us on: Twitter LinkedIn Facebook YouTube This communication contains information which is confidential and may also be privileged. It is for the exclusive use of the addressee. If you are not the addressee please note that any distribution, reproduction, copying, publication or use of this communication or the information is prohibited. If you have received this communication in error, please contact us immediately and also delete the communication from your computer. SanCloud Ltd. Registered Office: 164 Walkden Road, Worsley, Manchester, M28 7DP, UK. Company Registered in England & Wales, Reg No: 8154061 VAT No: GB 153 7871 85
-----Original Message-----
From: agl-dev-community@lists.automotivelinux.org <agl-dev-community@lists.automotivelinux.org> On Behalf Of Jan Simon Moeller Sent: 05 March 2020 17:49 To: agl-dev-community@lists.automotivelinux.org Subject: [agl-dev-community] RFC: Feedback on changes to the AGL CI Hi all! As the number our images grow, we also need to expand our coverage in what images we build beside 'agl-demo-platform'. In a first step, we enabled building these images for qemux86-64: - agl-image-graphical-html5 (aka the html5 'only' demo) - agl-demo-platform with agl-compositor enabled (aka the new compositor) Future candidates are the cluster image and the telematic image. Any other variants that should be considered ? This is now also a good time to change what boards get built. And I'd like to gather feedback on this: The proposal is to: - replace the rpi3 with the rpi4 - replace intel-corei7-64 with the combined 'qemux86-64' - remove the dra7xx-evm ('vayu') build ? This will free-up build-capacity. After that change we would run CI-builds for: - qemux86-64 (all variants: demo-platform, html5-only, agl-compositor) - R-Car m3ulcb(-nogfx) - R-Car h3ulcb(-nogfx) - qemuarm - qemuarm64 - rpi4 Any comments, suggestions or objections? Best regards, Jan-Simon ------ Jan-Simon Möller AGL Release Manager The Linux Foundation Visit us at: www.automotivegradelinux.org lists.automotivelinux.org www.linuxfoundation.org
|
|
|
|
Hi !
Thanks for the feedback. Based on this thread and the devcall, the updated plan is to - include agl-image-minmal in the default build flow (before / towards agl-demo-platform) (separate jira subtask) - add the cluster image and the telematic image (separate jira subtask) For the boards built for each patchset: - replace the rpi3 with the rpi4 - replace intel-corei7-64 with the combined 'qemux86-64' - remove m3ulcb-nogfx in favour of h3ulcb-nogfx (aka only h3) - replace the dra7xx-evm with the bbe This will free-up build-capacity. After that change we would run CI-builds for: - qemux86-64 (all variants: demo-platform, html5-only, agl-compositor) - R-Car h3ulcb(-nogfx) - qemuarm - qemuarm64 - rpi4 - bbe Any comments, suggestions or objections? We use https://jira.automotivelinux.org/browse/SPEC-3262 to track this. Best regards, Jan-Simon Möller
|
|
|