Christian Marangi 6099d083a6 CI: build: add checks to test if toolchain container can be used ... Add checks to test if toolchain container can be used. This is to handle case of new target or migration of any sort. If the toolchain container can't be found, the tools container is used instead. Signed-off-by: Christian Marangi <ansuelsmth@gmail.com> (cherry picked from commit 23a5c715a9)		2023-10-24 17:11:06 +02:00
..
scripts	ci: show_build_failures: fix missing output for configure failures	2023-01-09 11:22:10 +01:00
build-tools.yml	ci: use new buildbot worker images with Debian 11	2023-05-15 20:43:47 +02:00
build.yml	CI: build: add checks to test if toolchain container can be used	2023-10-24 17:11:06 +02:00
check-kernel-patches.yml	CI: rework build workflow to have split target and subtarget directly	2023-05-24 19:26:06 +01:00
coverity.yml	CI: rework build workflow to have split target and subtarget directly	2023-05-24 19:26:06 +01:00
Dockerfile.tools	ci: use new buildbot worker images with Debian 11	2023-05-15 20:43:47 +02:00
formal.yml	CI: bump actions/checkout action to v3	2022-10-12 16:47:46 +02:00
kernel.yml	CI: rework build workflow to have split target and subtarget directly	2023-05-24 19:26:06 +01:00
label-kernel.yml	CI: use toolchain container for label workflow	2023-05-28 03:47:01 +02:00
label-target.yml	CI: use toolchain container for label workflow	2023-05-28 03:47:01 +02:00
labeler.yml	CI: labeler: fix wrong label for pr targeting stable branch	2022-12-01 01:51:58 +01:00
packages.yml	CI: rework build workflow to have split target and subtarget directly	2023-05-24 19:26:06 +01:00
push-containers.yml	CI: push-containers: refresh containers also on modify cmake options	2023-10-04 13:30:52 +02:00
toolchain.yml	CI: rework build workflow to have split target and subtarget directly	2023-05-24 19:26:06 +01:00
tools.yml	ci: tools: run the job on changes in include directory as well	2023-05-23 21:41:44 +02:00