Closed gctucker closed 6 years ago
This seems to be working fine on staging, running regular builds mixed with bisections on the same builder with the lock. I just need to add a step at the end to trigger the arch-complete
job and this should be usable in place of single-defconfig-builder
.
Next step would be to make this job just build one defconfig, and move the logic to trigger a series of builds for all the ARCHs and defconfigs to a top-level trigger job combining what trigger-tarball
and defconfig-creator
are currently doing.
Got all the builds and boots as expected using this job: https://staging.kernelci.org/build/gtucker/branch/kernelci-test/kernel/kernelci-test-058-5-gcfff8c9d056b/ https://staging.kernelci.org/boot/all/job/gtucker/branch/kernelci-test/kernel/kernelci-test-058-5-gcfff8c9d056b/
Add jenkins/build.jpl as a Jenkins Pipeline alternative to kernel-single-defconfig-builder.sh which relies on Matrix. It takes the same set of parameters as the current jobs so it should be possible to use it in-place.
This uses the same lock as bisect.jpl, so several executors can be enabled on nodes with both "builder" and "bisection" labels set to let them share the server.
Signed-off-by: Guillaume Tucker guillaume.tucker@collabora.com