Closed wlfshmn closed 5 years ago
@wlfshmn An API to resolve a project via it's name and version doesn't exist. So currently, the use-case you're looking to achieve isn't supported.
I'll add a resolution API to the next feature release and add that functionality to the Jenkins plugin once available.
@stevespringett, I ran into the same issue last week. No problem... we can wait for the next feature release.
However, I am thinking... with a "resolve" API available, could one perhaps use this to have pipeline multibranch jobs automatically delete the matching project in Dependency-Track when the branch is deleted in the Jenkins job? Maybe using curl? Or perhaps by an extension to Dependency-Track plugin functionality?
The API for looking up a project by its name and version is complete. The defect reported in this ticket is specific to the Jenkins plugin, not Dependency-Track itself. The changes to the Jenkins plugin is being tracked in jenkinsci/dependency-track-plugin/pull/5
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Issue Type:
Current Behavior:
Invoking the plugin from a pipeline as follows:
Results in a correct upload of a BOM to Dependency-Track, but the synchronous polling fails as it expects a projectUuid and has none, as the invocation didn't supply one.
settings synchronous to false allows the step to complete, but without the benefits of synchronous mode.
Build logs show the following:
Dependency-track server logs contains the following:
Steps to Reproduce (if defect):
See above
Expected Behavior:
Ideally, findings should be retrievable with name/version as well as uuid. Alternativly, the plugin should check for a missing uuid and logs this functional limitation.
Environment:
Other Details:
(e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)