(sending from other email address, since arm one isn't signed up for this mailing list)
Let me know if you want help setting up Gitlab CI. It can be a little non-obvious, and I've been fiddling with it a bit. Also, I'd recommend looking at runfvp in meta-arm. Since there is a public fvp machine for morello, it can really help with regressions. https://gitlab.com/jonmason00/meta-arm/-/blob/master/scripts/runfvp and referencing the fvp-base bits to get it working as a starting point to work off of https://gitlab.com/jonmason00/meta-arm/-/blob/master/meta-arm-bsp/conf/machi...
Thanks, Jon
On Tue, Nov 29, 2022 at 9:52 AM Pawel Zalewski < pzalewski@thegoodpenguin.co.uk> wrote:
Hi all,
Given that you've already integrated KAS with your CI I think it is the right choice forward. Many thanks for all of the links !
Kind regards, Pawel
On Tue, 29 Nov 2022 at 14:42, Alex Lennon ajlennon@dynamicdevices.co.uk wrote:
On 29 Nov 2022, at 14:34, Jon Mason jon.mason@arm.com wrote:
We really are big fans of KAS. I'm giving a talk on it tomorrow at the Yocto Summit https://summit.yoctoproject.org/yocto-project-summit-2022-11/talk/BZNRTF/
We can help you with the setup, but it REALLY shines in CI. We use it for Gitlab CI, and I would highly recommend you do something similar. See https://gitlab.com/jonmason00/meta-arm/-/pipelines for a publicly visible version of the CI we do for meta-arm.
Thanks for the reminder! I’ll take a look at the schedule. I put some time into bringing meta-mono CI under control recently.
Would be very interesting to see what I’d have to do to tidy up and move to KAS…
[image: meta-mono.png]
meta-mono/CI_github.yml at master · DynamicDevices/meta-mono https://github.com/DynamicDevices/meta-mono/blob/master/.github/workflows/CI_github.yml github.com https://github.com/DynamicDevices/meta-mono/blob/master/.github/workflows/CI_github.yml
https://github.com/DynamicDevices/meta-mono/blob/master/.github/workflows/CI_github.yml
Cheers,
Alex
Thanks, Jon
-----Original Message----- From: Ross Burton Ross.Burton@arm.com Sent: Tuesday, November 29, 2022 8:59 AM To: Pawel Zalewski pzalewski@thegoodpenguin.co.uk Cc: Vincenzo Frascino Vincenzo.Frascino@arm.com; Alex J Lennon < ajlennon@dynamicdevices.co.uk>; Andrew Murray < amurray@thegoodpenguin.co.uk>; Manjunatha Mulki Bhat manjubhat@gmail.com; Steve Capper Steve.Capper@arm.com; Jon Mason Jon.Mason@arm.com; linux-morello-distros@op-lists.linaro.org Subject: Re: [linux-morello-distros] Yocto on Morello Round Table
On 29 Nov 2022, at 11:34, Pawel Zalewski pzalewski@thegoodpenguin.co.uk wrote:
Hi Vincenzo,
The manifest is there to fetch the meta-arm layer as meta-morello
appends recipes found in the meta-arm's bsp, the manifest will also
fetch Yocto kirkstone and meta-morello itself. So at the end the developer will end up with a checkout of kirkstone with meta-arm and meta-morello placed inside its poky tree.
FWIW, in meta-arm we’re big fans of Kas (https://kas.readthedocs.io/). It integrates with Yocto so does more than just fetching, and doesn’t involve another repository just for the manifest.
Ross
linux-morello-distros mailing list -- linux-morello-distros@op-lists.linaro.org To unsubscribe send an email to linux-morello-distros-leave@op-lists.linaro.org
linux-morello-distros mailing list -- linux-morello-distros@op-lists.linaro.org To unsubscribe send an email to linux-morello-distros-leave@op-lists.linaro.org
