cve-pipeline: add FORCE parameter

cve-pipeline runs the ceph-dev-pipeline Jenkinsfile, which consults
FORCE to decide whether to rebuild and re-upload when artifacts already
exist in Chacra or Pulp.  Without the parameter, env.FORCE is unset and
a CVE rebuild of an already-uploaded sha1 always skips compilation with
no way to override short of THROWAWAY=true.

Also sync the THROWAWAY description with ceph-dev-pipeline's.

Signed-off-by: David Galloway <david.galloway@ibm.com>

diff --git a/cve-pipeline/config/definitions/cve-pipeline.yml b/cve-pipeline/config/definitions/cve-pipeline.yml
index 2ad5cd0290efb64678648f9d5410f3e01efc5b95..5cc40607a45678c849c298d189390713c9a38957 100644 (file)
--- a/cve-pipeline/config/definitions/cve-pipeline.yml
+++ b/cve-pipeline/config/definitions/cve-pipeline.yml
@@ -69,7 +69,12 @@
 
       - bool:
           name: THROWAWAY
-          description: "Whether to push any binaries to Chacra or Pulp.  Overrides CHACRA_UPLOAD and PULP_UPLOAD if either are true."
+          description: "Whether to push any binaries to Chacra or Pulp. Overrides CHACRA_UPLOAD and PULP_UPLOAD if either are true."
+          default: false
+
+      - bool:
+          name: FORCE
+          description: "Whether to push new binaries even if some are already present"
           default: false
 
       - bool: