Fix: use build.getBuildVariables to get FORCE_JOB_RUN

Signed-off-by: Jonathan Rajotte <jonathan.rajotte-julien@efficios.com>

diff --git a/scripts/system-tests/system-trigger.groovy b/scripts/system-tests/system-trigger.groovy
index c4fd5343d5dc2ae71864ad5c757d4525bdec0da8..9736b02376dc4727dc3722ef84a07aa40a1e2b43 100644 (file)
--- a/scripts/system-tests/system-trigger.groovy
+++ b/scripts/system-tests/system-trigger.groovy
@@ -398,7 +398,8 @@ currentJobs.each { jobName, jobInfo ->
   // If the job ran in the past, we check if the IDs changed since.
   // Fetch past results only if the job is not of type canary or fuzzing.
   if (!jobName.contains('_canary') && !jobName.contains('_fuzzing') &&
-         pastJobs.containsKey(jobName) && !params.FORCE_JOB_RUN) {
+         pastJobs.containsKey(jobName) &&
+         build.getBuildVariables().get('FORCE_JOB_RUN') == 'false') {
     pastJob = pastJobs[jobName];
 
     // If the code has not changed report previous status.