Modify pass threshold to 100 for stage3-patch workflow

Change-Id: Ic11bdc47d0fc50f475c9b56c9628bce303d4d30a
Signed-off-by: garciadeblas <gerardo.garciadeblas@telefonica.com>

jenkins/ci-pipelines/ci_stage_1.groovy

@@ -89,6 +89,8 @@ node("${params.NODE}") {
                 println("disabling stage_3 invocation")
                 return
             }
+            // in this case, since this is for daily jobs, the pass threshold for robot tests should be adapted
+            downstream_params.add(string(name: 'ROBOT_PASS_THRESHOLD', value: '99.0'))
         }
         // callout to stage_2.  This is a multi-branch pipeline.
         downstream_job_name = "${mdg}-${stage_name}/${GERRIT_BRANCH}"

jenkins/ci-pipelines/ci_stage_3.groovy

@@ -46,7 +46,7 @@ properties([
         string(defaultValue: '/home/jenkins/hive/kubeconfig.yaml', description: '', name: 'KUBECONFIG'),
         string(defaultValue: '/home/jenkins/hive/clouds.yaml', description: '', name: 'CLOUDS'),
         string(defaultValue: 'Default', description: '', name: 'INSTALLER'),
-        string(defaultValue: '99.0', description: '% passed Robot tests to mark the build as passed', name: 'ROBOT_PASS_THRESHOLD'),
+        string(defaultValue: '100.0', description: '% passed Robot tests to mark the build as passed', name: 'ROBOT_PASS_THRESHOLD'),
         string(defaultValue: '80.0', description: '% passed Robot tests to mark the build as unstable (if lower, it will be failed)', name: 'ROBOT_UNSTABLE_THRESHOLD'),
     ])
 ])