Hi Stefano, > -----Original Message----- > From: Stefano Stabellini <sstabell...@kernel.org> > Subject: Re: [PATCH 1/9] automation: Use custom build jobs when extra > config options are needed > > On Thu, 22 Sep 2022, Michal Orzel wrote: > > Currently, all the arm64 defconfig build jobs, regardless of the > > container used, end up building Xen with the extra config options > > specified in the main build script (e.g. CONFIG_EXPERT, > > CONFIG_STATIC_MEMORY). Because these options are only needed for > > specific test jobs, the current behavior of the CI is incorrect > > as we add the extra options to all the defconfig builds. This means > > that on arm64 there is not a single job performing proper defconfig build. > > > > To fix this issue, add custom build jobs each time there is a need for > > building Xen with additional config options. Introduce EXTRA_XEN_CONFIG > > variable to be used by these jobs to store the required options. This > > variable will be then read by the main build script to modify the .config > > file. This will also help users to understand what is needed to run specific > > test. > > > > Signed-off-by: Michal Orzel <michal.or...@amd.com> > > --- > > This patch could actually be consider to be taken for 4.17 release. > > The reason why is because currently our CI for arm64 does not even > > peform clean defconfig build which is quite crucial target to be tested. > > Performing builds always with EXPERT and UNSUPPORTED is not something > so > > beneficial for release tests. This is up to the release manager. > > + Henry > > I agree this should go in 4.17, so that gitlab-ci can test non-DEBUG > builds on ARM.
Yes sure, I agree once this series is properly reviewed, this can be merged to 4.17. Kind regards, Henry
