You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When the Jenkins with a stage as follow:
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:
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: