You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue - Feature Request
When publishing a new version to Dependency Track of an existing project, the audit history is not cloned. When you add a new version in the UI you have the option to clone various data. Are there properties available to enable this using the Jenkins plugin? (Could be that I overlooked this in the documentation)
Use case:
Project v1.0.0 has 15 vulnerabilities. Various audit trails and statuses have been added to the project version. New version Project v1.0.1 is published but all the auditing info needs to be re-added.
Used Versions
Dependency-Track v4.3.6
OWASP Dependency-Track Plugin v4.0.0
The text was updated successfully, but these errors were encountered:
For cloning, the ID of the project to be cloned is required. In DT there is no predecessor relationship. The DT frontend knows which project to clone because it uses the currently open project. The Jenkins plugin would either need the ID of the project to clone or would have to look up all the versions with the same project name, sort them somehow, and then make the clone call. This would make things too complicated. Therefore, I reject this feature request.
Issue - Feature Request
When publishing a new version to Dependency Track of an existing project, the audit history is not cloned. When you add a new version in the UI you have the option to clone various data. Are there properties available to enable this using the Jenkins plugin? (Could be that I overlooked this in the documentation)
Use case:
Project v1.0.0 has 15 vulnerabilities. Various audit trails and statuses have been added to the project version. New version Project v1.0.1 is published but all the auditing info needs to be re-added.
Used Versions
Dependency-Track v4.3.6
OWASP Dependency-Track Plugin v4.0.0
The text was updated successfully, but these errors were encountered: