Our Gitlab pipeline is currently broken up in to several stages. This was done with the thought process of "we should test tools and if they're good test emulated targets and if they're good test real hardware and if they're good test the world". However, in terms of that first stage it only really matters that binman, et al are still functional. And for a few years now Gitlab has had a "needs" keyword that lets you refine pipeline dependencies. Use this to perform the minor optimization of having test.py only require that tool testing job. This will become more useful later when we add long running testsuites that we do not want to block later jobs.
Signed-off-by: Tom Rini trini@konsulko.com --- More specifically, after talking with Ilias we will get the SystemReady IR ACS testsuite as a possible job in CI. But it takes ages to complete, so we'll be (a) running it only on tagged releases and (b) want to make sure it doesn't the rest of the pipeline. --- .gitlab-ci.yml | 1 + 1 file changed, 1 insertion(+)
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index 2164ad79a72b..807837b6e118 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -23,6 +23,7 @@ stages: .buildman_and_testpy_template: &buildman_and_testpy_dfn stage: test.py retry: 2 # QEMU may be too slow, etc. + needs: [ "Run binman, buildman, dtoc, Kconfig and patman testsuites" ] rules: - when: always before_script: