jfrog / jfrog/jfrog-cli-security

Add `rescan` option to JFrogBuildScan task

Open
#893 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

The JFrogBuildScan@1 task does not currently expose JFrog CLI's --rescan option.

This would be useful when a build has already been successfully scanned and needs to be scanned again, for example after an Xray ignore rule has been added or changed.

It is also relevant for pipelines where the build is scanned during CI but deployment takes place significantly later. In that case, teams may want to explicitly rescan the same build as part of the deployment process rather than rely solely on the earlier scan result.

Could a rescan boolean input/checkbox be added to the task, defaulting to false?

For example:

- task: JFrogBuildScan@1
  inputs:
    xrayConnection: 'jfrog xray token'
    buildName: '$(Build.DefinitionName)'
    buildNumber: '$(Build.BuildNumber)'
    allowFailBuild: true
    vuln: false
    rescan: true

This would pass the equivalent of --rescan to the underlying jf build-scan command.

A dedicated boolean input seems preferable to a generic arguments field, as --rescan is a specific option of the Build Scan command and can be clearly exposed through both the task UI and YAML.

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 at the JFrogBuildScan@1 task definition and trace how its inputs reach the underlying jf build-scan invocation. Add the rescan boolean with a false default, expose it in the task UI and YAML, and verify that enabling it passes --rescan.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
ci-cd
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.