jfrog / jfrog/jfrog-cli-security

jfrog xray scan report integration with AzureDevops CLI task

Open
#430 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

We are using Azuredevops Jfrog tasks to build our mvn/npm/gradle projects and, using the below jfrog publish buildinfo and scan task to get the violation list. But as part of the same pipeline , we are planning for automated way (either by CLI or Azuredevops task) to create a report in xray by including the pipeline used "source Repo" and the build scope of the same pipeline.

Tried the XRAY api options, but failed to to generate it dynamically as part of the pipeline with these dynamic scopes.

  - task: JFrogPublishBuildInfo@1
    name: publishBInfo
    displayName: 'Publish Build Info to JFrog'
    condition: succeeded()
    inputs:
      artifactoryConnection: 'myserviceconnection'
      buildName: '$(Build.DefinitionName)'
      buildNumber: '$(Build.BuildNumber)'

  - task: JFrogBuildScan@1
    enabled: false
    name: xrayScan
    displayName: 'Security Scan'
    condition: succeeded()
    inputs:
      xrayConnection: 'myserviceconnection'
      buildName: '$(Build.DefinitionName)'
      buildNumber: '$(Build.BuildNumber)'
      allowFailBuild: true
      vuln: true

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

Review the JFrogPublishBuildInfo@1 and JFrogBuildScan@1 pipeline tasks and the Xray API options described in the issue. Define how the pipeline's source repository and dynamic build scope should be passed, then validate that an automated Xray report can be created for the same pipeline.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, go
Domain
devops, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.