jfrog / jfrog/jfrog-cli-security

build-info icon not showing

Open
#447 0 comments 1 reaction 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

How can we help?

Anything special needs to be configured for this to work?
I'm using latest plugging version with Jenkins LTS.

Running this simple nuget build, which completes successfully.
I can see the build-info and scan results in Artifactory, but the build-info and the xray icons are missing.
Not sure if the xray icon is supported, but I understand it should support the build-info icon.

jf 'nuget-config --repo-resolve  Nuget --server-id-resolve default-server'
jf 'nuget restore test.sln -MSBuildPath c:\\...\\2022\\Professional\\MSBuild\\Current\\Bin\\ -Recursive -Force --build-name=${buildName} --build-number=${buildNum}'
 jf 'rt build-publish ${buildName} ${buildNum}'

script {
      try {
                jf 'build-scan ${buildName} ${buildNum}'
       }
        catch (err) {
                  println 'Violations were found!'
         }

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 by reproducing the Jenkins LTS NuGet build with the JFrog CLI commands shown in the report. Check the plugin and build-scan configuration to determine whether build-info and Xray icons are supported; done means the required behavior is confirmed and the missing-icon cause is documented or resolved.

Written by the indexing model from the issue text.

Assessment

Domain
ci-cd, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.