index.md: ECLAIR: Make explicit that delta job runs on Allow-CI+1/+2
This corresponds to the change done to the job config earlier.
Also, reword the delta job description to be more clear and correspond
to the current state of affairs (it was originally written yet when
the job run automatically without Allow-CI label).
Signed-off-by: Paul Sokolovsky <paul.sokolovsky@linaro.org>
Change-Id: I8c5133d79408875ec7e322944b8d97e8506efbbe
diff --git a/docs/index.md b/docs/index.md
index c6c01d7..d2a8dd3 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -550,11 +550,12 @@
this job tests patches submitted to Gerrit, and is intended to help with
reviews, the aim being that a patch doesn't introduce *new*
MISRA issues, even if the codebase in general has some number of issues,
- which can't be addressed short-term (or at all). To provide quick
- turnaround and reasonable system load, this job is currently builds
- just a single TF-A configuration, and is triggered by assigning
- `Allow-CI+1` label. This may change in the future when more configurations
- are added to processing.
+ which can't be addressed short-term (or at all). The job is triggered by
+ assigning `Allow-CI+1`/`Allow-CI+2` label to a review, similar to other
+ CI jobs testing individual patches. To provide quick turnaround and
+ reasonable system load, this job is currently builds just a single TF-A
+ configuration. This may change in the future when more configurations
+ are added to the workflow.
Both jobs are structured as matrix jobs, with the single axis being a TF-A
platform. ECLAIR reports are publish as job artifacts. For each job, they are: