Replies: 2 comments
-
This has nothing to do with the plugin. It is about how Dependency-Track itself works. Every combination of name and version is treated as a new project in Dependency-Track. You can implement the steps you want yourself using a scripted pipeline. You have everything you need. You have the API key and you have the plugin to perform the upload. The rest is just two more API calls you need to make. Another option is to use the stage name as the version, for example name="demo" and version="prod". This is not ideal, as it only makes sense if only one version of demo can be active per stage at a time. |
Beta Was this translation helpful? Give feedback.
-
Thanks for your reply. I can understand the use case where is important keep tracked each version as new project, but in my case only the latest version for each environment is important. I implemented a function
Have a nice day 👋 |
Beta Was this translation helpful? Give feedback.
-
Hello, i'm evaluating dependency track and dependency track jenkins plugin to collect and analyze vulnerable components for docker images and node, python, .net core, java applications. At the moment i'm facing with an issue on how to handle project updates when a CI pipeline run.
My idea is to handle a project for each deployment environment with his own version. Something like this:
However with the actual behaviour of the jenkins plugin i can not obtain that kind of projects organization, but i have something like this:
Is there any way to configure the plugin to will work with the following steps?
Thanks in advance
Beta Was this translation helpful? Give feedback.
All reactions