feat(evidence): Add JFrog Evidence task (jf evd create-evidence) - #649
Open
tiwarishrijan wants to merge 2 commits into
Open
feat(evidence): Add JFrog Evidence task (jf evd create-evidence)#649tiwarishrijan wants to merge 2 commits into
tiwarishrijan wants to merge 2 commits into
Conversation
tiwarishrijan
marked this pull request as ready for review
August 18, 2026 18:09
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Implements the JFrog Evidence Azure DevOps extension task, wrapping the JFrog CLI's
jf evd create-evidencecommand. The task lets users attach signed, predicate-based evidence (SLSA/custom attestations) to a build, release bundle, package, application, or arbitrary repository path, with optional local/Artifactory attachments and DSSE signing (private key or pre-signed Sigstore bundle).Changes
New task —
tasks/JFrogEvidence/evidence.ts— builds and executes thejf evd create-evidenceCLI command:--predicate,--predicate-type,--markdown,--integration sonar)--key,--key-alias,--sigstore-bundle)subjectTypepicker: build, release bundle, package, application, or repository path (--build-name/--build-number,--release-bundle/--release-bundle-version,--package-name/--package-repo-name/--package-version,--application-key/--application-version,--subject-repo-path/--subject-sha256)attachmentSourcepicker: local file (--attach-local+--attach-artifactory-temp-path) or existing Artifactory path (--attach-artifactory-path)--provider-id,--type,--project,--formattask.json— full input schema, grouped into Predicate / Signing / Subject / Attachments / Advanced UI sections withvisibleRules so incompatible fields (e.g. predicate/key fields when a Sigstore bundle is supplied) auto-hidepackage.json,icon.png,.gitignore— standard task scaffoldingTests
tests/testUtils.ts— addedevidencetask path exporttests/resources/evidence/— new fixtures and mock-task scripts:upload.js/createOnPath.js— evidence attached to a repository-path subjectbuildUpload.js/buildPublish.js/createOnBuild.js— evidence attached to a build subject, including a local-file attachmenttests/tests.ts— newEvidence Testssuite (gated byADO_SKIP_TESTS=evidence)Misc
package.json— added@types/semverdev dependencyCLI integration
Wraps
jf evd create-evidence(see JFrog CLI Evidence docs).Checklist
devbranch.npm run formatfor formatting the code before submitting the pull request.