From 7aab161e06d67b7c331648e2526723839b247928 Mon Sep 17 00:00:00 2001 From: Jonathan Rajotte Date: Wed, 1 May 2019 11:32:48 -0400 Subject: [PATCH] Fix: use build.getBuildVariables to get FORCE_JOB_RUN Signed-off-by: Jonathan Rajotte --- scripts/system-tests/system-trigger.groovy | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/scripts/system-tests/system-trigger.groovy b/scripts/system-tests/system-trigger.groovy index c4fd534..9736b02 100644 --- 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. -- 2.34.1