jfrog / jfrog/jfrog-cli-security

JFrog plugin - Local jfrog CLI Scan result output into a Junit-formatted file

Open
#445 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature request
Dominant language
Go
Stars
13
Forks
50
Avg merge
3d 48m
Merged PRs (30d)
26

Description

Is your feature request related to a problem? Please describe.

When the Jenkins with a stage as follow:

stage('Apply JFrog X-Ray Scanning') {
tools { jfrog 'jfrog-cli' }
steps {
	script {					
		// Show the installed version of JFrog CLI.
		jf '-v'
		
		// Show the configured JFrog Platform instances.
		jf 'c show'
		
		// Ping Artifactory.
		jf 'rt ping'

		// Start local X-Ray scan
		jf "scan ${WORKSPACE}/**/my-artifact.tar.gz"
	}
}

The scan results are shown in the build log/stdout as a table (the default format).
Such output would be very useful in the Jenkins build if it could be persisted as a build artifact (with the archiveArtifacts step) or as tests results (with the Junit step).

Describe the solution you'd like to see

Multiple approaches on the matter:

  • JFrog plugin to allow outputting the CLI stdout into a file in the build workspace
  • jfrog-cli scan to support the junit format and allow outputting it into a file
Describe alternatives you've considered

No response

Additional context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the JFrog CLI scan command and the Jenkins pipeline example in the issue, then determine whether output-file support or JUnit formatting belongs in this repository. Done means scan results can be written to a workspace file suitable for archiveArtifacts or Jenkins JUnit processing, with the chosen behavior documented and verified.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli, testing
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.