chore(Jenkinsfile): Remove the VULNERABLE_CODE_API_KEY parameter

Firstly, VulnerableCode can be used without an API key now [1], and secondly the code to configure the API key was outdated anyway as it was not adjusted to [2]. Simply remove the code to address this. If the need to specify an API key should reoccur, the feature introduced in 738790c should be used to set it via an environment variable that is being used in a `config.yml` template. [1]: aboutcode-org/vulnerablecode#1352 [2]: #7690 Signed-off-by: Sebastian Schuberth <[email protected]>
oss-review-toolkit · Nov 30, 2023 · a464678 · a464678
1 parent 4bf0241
commit a464678
Showing 1 changed file with 1 addition and 12 deletions.
diff --git a/integrations/jenkins/Jenkinsfile b/integrations/jenkins/Jenkinsfile
@@ -192,12 +192,6 @@ pipeline {
             defaultValue: true
         )
 
-        string(
-            name: 'VULNERABLE_CODE_API_KEY',
-            description: 'Optional API key to enable VulnerableCode (see https://public.vulnerablecode.io/account/request_api_key/).',
-            defaultValue: ''
-        )
-
         /*
          * ORT evaluator tool parameters.
          */
@@ -618,12 +612,7 @@ pipeline {
                             ORT_OPTIONS="$ORT_OPTIONS --stacktrace"
                         fi
 
-                        ADVISOR_OPTIONS="-a OSV"
-
-                        if [ -n "$VULNERABLE_CODE_API_KEY" ]; then
-                            ORT_OPTIONS="$ORT_OPTIONS -P ort.advisor.vulnerableCode.apiKey=$VULNERABLE_CODE_API_KEY"
-                            ADVISOR_OPTIONS="$ADVISOR_OPTIONS,VulnerableCode"
-                        fi
+                        ADVISOR_OPTIONS="-a OSV,VulnerableCode"
 
                         /opt/ort/bin/ort $ORT_OPTIONS advise $ADVISOR_OPTIONS -i out/results/current-result.yml -o out/results/advisor
                         '''.stripIndent().trim()