Add providerId for multiple integrations

.github/workflows/blazemeter-evidence-example.yml

@@ -92,4 +92,5 @@ jobs:
           --key-alias "${{ secrets.PRIVATE_KEY_ALIAS }}" \
           --predicate "blazemeter-predicate.json" \
           --predicate-type "http://blazemeter.com/performance-results/v1" \
+          --provider-id "blazemeter" \
           ${{ env.ATTACH_OPTIONAL_MARKDOWN_TO_EVIDENCE == 'true' && '--markdown "blazemeter-results.md"' || '' }}

.github/workflows/cypress-evidence-example.yml

@@ -74,4 +74,5 @@ jobs:
           --key-alias "${{ secrets.PRIVATE_KEY_ALIAS }}" \
           --predicate "reports/overall-report.json" \
           --predicate-type "http://cypress.io/test-results/v1" \
+          --provider-id "cypress" \
           ${{ env.ATTACH_OPTIONAL_MARKDOWN_TO_EVIDENCE == 'true' && '--markdown "reports/cypress-results.md"' || '' }}

.github/workflows/jira-evidence-example.yml

@@ -85,5 +85,6 @@ jobs:
             --key-alias "${{ vars.EVIDENCE_KEY_ALIAS }}" \
             --predicate ./examples/jira/helper/transformed_jira_data.json \
             --predicate-type http://atlassian.com/jira/issues/v1 \
+            --provider-id "jira" \
             ${{ env.ATTACH_OPTIONAL_CUSTOM_MARKDOWN_TO_EVIDENCE == 'true' && '--markdown "examples/jira/helper/transformed_jira_data.md"' || '' }}
 

.github/workflows/junit-evidence-example.yml

@@ -97,6 +97,7 @@ jobs:
               --key-alias "${{ vars.EVIDENCE_KEY_ALIAS }}" \
               --predicate ./target/consolidated-test-report.json \
               --predicate-type https://jfrog.com/evidence/junit-test-results/v1 \
+              --provider-id "junit" \
               ${{ env.ATTACH_OPTIONAL_CUSTOM_MARKDOWN_TO_EVIDENCE == 'true' && '--markdown "junit-results.md"' || '' }}
           else
             echo "No test results found to attach as evidence"

.github/workflows/testRail-evidence-example.yml

@@ -86,4 +86,5 @@ jobs:
           --key-alias "${{ secrets.PRIVATE_KEY_ALIAS }}" \
           --predicate "reports/overall-report.json" \
           --predicate-type "http://testrail.com/test-results" \
+          --provider-id "testrail" \
           ${{ env.ATTACH_OPTIONAL_MARKDOWN_TO_EVIDENCE == 'true' && '--markdown "reports/results.md"' || '' }}

examples/blazemeter/README.md

@@ -160,6 +160,7 @@ Once the workflow completes successfully, you can navigate to your repository in
     --key-alias "$PRIVATE_KEY_ALIAS" \
     --predicate "blazemeter-predicate.json" \
     --predicate-type "http://blazemeter.com/performance-results/v1" \
+    --provider-id "blazemeter" \
     ${{ env.ATTACH_OPTIONAL_MARKDOWN_TO_EVIDENCE == 'true' && '--markdown "blazemeter-results.md"' || '' }}
   ```
 

examples/cypress/README.md

@@ -105,6 +105,7 @@ This final step uses `jf evd create` to attach the test results to the Docker im
     --key-alias "${{ secrets.PRIVATE_KEY_ALIAS }}" \
     --predicate "reports/overall-report.json" \
     --predicate-type "http://cypress.io/test-results/v1" \
+    --provider-id "cypress" \
     [--markdown "reports/cypress-results.md"]
   ```
     The --markdown flag is included only if ATTACH_OPTIONAL_MARKDOWN_TO_EVIDENCE is set to true.

examples/jenkins-provenance/Jenkinsfile

@@ -9,6 +9,7 @@ pipeline {
             MARKDOWN_FILE_NAME = 'JenkinsSLSA.md'
             PREDICATE_FILE_NAME = '${PROJECT_WORKING_DIR}/predicate.json'
             PREDICATE_TYPE = 'http://slsa.dev/provenance/v1'
+            PROVIDER_ID = 'jenkins'
     }
     stages {
         stage('Checkout') {
@@ -65,6 +66,7 @@ pipeline {
             --key-alias ${KEY_ALIAS} \
             --predicate ${PREDICATE_FILE_NAME} \
             --predicate-type ${PREDICATE_TYPE} \
+            --provider-id ${PROVIDER_ID} \
             --markdown ${MARKDOWN_FILE_NAME}'
             }
         }

examples/jira/README.md

@@ -230,6 +230,7 @@ jf evd create \
     --key-alias "${{ vars.EVIDENCE_KEY_ALIAS }}" \
     --predicate ./examples/jira/helper/transformed_jira_data.json \
     --predicate-type http://atlassian.com/jira/issues/v1 \
+    --provider-id "jira" \
     ${{ env.ATTACH_OPTIONAL_CUSTOM_MARKDOWN_TO_EVIDENCE == 'true' && '--markdown "examples/jira/helper/transformed_jira_data.md"' || '' }}
 ```
 

examples/junit/README.md

@@ -167,6 +167,7 @@ jf evd create \
   --key-alias "${{ vars.EVIDENCE_KEY_ALIAS }}" \
   --predicate ./target/consolidated-test-report.json \
   --predicate-type http://junit.org/test-results \
+  --provider-id "junit" \
   --markdown "junit-results.md"
 ```
 

examples/testRail/README.md

@@ -126,6 +126,7 @@ You can trigger the workflow manually from the GitHub Actions tab. The workflow
   --key-alias "${{ secrets.PRIVATE_KEY_ALIAS }}" \
   --predicate "reports/overall-report.json" \
   --predicate-type "http://testrail.com/test-results" \
+  --provider-id "testrail" \
   [--markdown "reports/results.md"]
   ```
     The --markdown flag is included only if ATTACH_OPTIONAL_MARKDOWN_TO_EVIDENCE is set to true.