Message ID | 20250207150439.392479-5-Sai.Sathujoda@toshiba-tsip.com (mailing list archive) |
---|---|
State | New |
Headers | show |
Series | Automate CIP Core testing on M-COM x86 in LAVA | expand |
On 07.02.25 16:04, Sai.Sathujoda@toshiba-tsip.com wrote: > From: sai ashrith sathujoda <sai.sathujoda@toshiba-tsip.com> > > Signed-off-by: sai ashrith sathujoda <sai.sathujoda@toshiba-tsip.com> > --- > .gitlab-ci.yml | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml > index 0459604..2e3054c 100644 > --- a/.gitlab-ci.yml > +++ b/.gitlab-ci.yml > @@ -231,6 +231,7 @@ build:x86-uefi-secure-boot: > targz: disable > watchdog: disable > security_test: enable > + build_swu_v2: enable > > build:qemu-amd64-swupdate: > extends: While we are onboarding the MCOM, we can do this both for the physical and the virtual amd64 target. However, I would like to revisit later on if we actually need both in the end. We should always try to keep our pipelines lean. Jan
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index 0459604..2e3054c 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -231,6 +231,7 @@ build:x86-uefi-secure-boot: targz: disable watchdog: disable security_test: enable + build_swu_v2: enable build:qemu-amd64-swupdate: extends: