ci: enable LAVA boot and smoke tests on qemu devices for new MRs

Given test scope for new MRs is not defined yet and we only have one rpi4, b68 and c61 in the warsaw lab which are occupied mostly by daily scheduled pipeline, starting with boot and smoke tests on qemu devices is a good starting point for per MR testing.

.lava-test-scheduled extends .lava-test and is scheduled pipeline only. Long run jobs like ltp should extends the .lava-test-scheduled. Jobs that extend .lava-test will be added to MR's pipeline and scheduled pipeline.

Solves #486 (closed).

Signed-off-by: Chase Qi chase.qi@linaro.org

.oniro-ci/test-generic.yaml

@@ -12,6 +12,7 @@
     GIT_STRATEGY: none
     CI_LAVA_INSTANCE: "https://lava.ostc-eu.org/"
     CI_SQUAD_INSTANCE: "https://squadp.svc.ostc-eu.dev"
+    CI_SQUAD_PROJECT_NAME: "oniro-test-mr"
     # Run the same ltp test suites that using by LKFT project.
     # Reference: https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-5.10.y/build/v5.10.98-75-g9f5cb871ceb9/testjobs/
     LTP_TST_CMDFILES: "cap_bounds cpuhotplug crypto nptl pty securebits fs controllers hugetlb mm tracing containers io dio syscalls math commands ipc fcntl-locktests filecaps fs_bind fs_perms_simple fsx sched cve"
@@ -71,16 +72,22 @@
     # Submit the jobs to SQUAD.
     - |
       for job_def in $(find lava_jobs/ -name "*.yaml"); do
-        echo $CI_SQUAD_INSTANCE/api/submitjob/oniro-core/$CI_PROJECT_NAME/$CI_PIPELINE_ID/$MACHINE --header "Auth-Token: $CI_SQUAD_TOKEN"  --form "backend=oniro_lava" --form "definition=@${job_def}"
-        curl $CI_SQUAD_INSTANCE/api/submitjob/oniro-core/$CI_PROJECT_NAME/$CI_PIPELINE_ID/$MACHINE --header "Auth-Token: $CI_SQUAD_TOKEN"  --form "backend=oniro_lava" --form "definition=@${job_def}"
+        echo $CI_SQUAD_INSTANCE/api/submitjob/oniro-core/$CI_SQUAD_PROJECT_NAME/$CI_PIPELINE_ID/$MACHINE --header "Auth-Token: $CI_SQUAD_TOKEN"  --form "backend=oniro_lava" --form "definition=@${job_def}"
+        curl $CI_SQUAD_INSTANCE/api/submitjob/oniro-core/$CI_SQUAD_PROJECT_NAME/$CI_PIPELINE_ID/$MACHINE --header "Auth-Token: $CI_SQUAD_TOKEN"  --form "backend=oniro_lava" --form "definition=@${job_def}"
       done
       # Attach a callback to this build to trigger the lava-report job
       squad_build_id="$(curl --silent "$CI_SQUAD_INSTANCE/api/builds/?version=$CI_PIPELINE_ID" | jq -r '.results[0].id')"
-      curl -X POST $CI_SQUAD_INSTANCE/api/builds/$squad_build_id/callbacks/ --header "Authorization: Token $CI_SQUAD_TOKEN" -F "callback_url=$CALLBACK_URL"
+      curl --silent \
+        -X POST "$CI_SQUAD_INSTANCE/api/builds/$squad_build_id/callbacks/" \
+        -H "Authorization: Token $CI_SQUAD_TOKEN" \
+        -F "callback_url=$CALLBACK_URL" \
+        -F "callback_record_response=true"
   artifacts:
     paths:
       - lava_jobs/*.yaml
   rules:
+    - if: '$CI_SQUAD_TOKEN == null'
+      when: never
     # Run the build when it is scheduled.
     - if: $CI_PIPELINE_SOURCE == "schedule"
     # Do not run pipelines for draft merge requests unless manually triggered.
@@ -106,13 +113,18 @@
       # Get the test_runs_incomplete value from build status. That will tell
       # us if any of the LAVA jobs failed and we can determine whether the
       # report job is successful or not.
-      incomplete="$(curl --silent $CI_SQUAD_INSTANCE/api/builds/$CI_PIPELINE_ID/status/ | jq -r '.test_runs_incomplete')"
+      set -x
+      squad_build_id="$(curl --silent "$CI_SQUAD_INSTANCE/api/builds/?version=$CI_PIPELINE_ID" | jq -r '.results[0].id')"
+      incomplete="$(curl --silent $CI_SQUAD_INSTANCE/api/builds/$squad_build_id/status/ | jq -r '.test_runs_incomplete')"
       if [ "$incomplete" != "0" ]; then
         echo "ERROR: Incomplete test job reported: exit code 1"
         exit 1
       fi
+      set +x
 
   rules:
+    - if: '$CI_SQUAD_TOKEN == null'
+      when: never
     # Run the build when it is scheduled.
     - if: $CI_PIPELINE_SOURCE == "schedule"
       when: manual