Changes for page Dependency-Track

Last modified by Milad Afshar-Jahanshahi on 2025/09/03 14:31

From version 53.5
edited by Boris Folgmann
on 2025/09/03 14:17
Change comment: There is no comment for this version
To version 53.6
edited by Boris Folgmann
on 2025/09/03 14:21
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -53,7 +53,8 @@
53 53  
54 54  = Projects =
55 55  
56 -After creating a DevOps project in the portal, a Dependency-Track project is automatically created. The type of the new project is a **Collection Project**. Sub projects (for example, individual modules of a Maven project) are created as children of the DevOps portal project. This makes it easier to see aggregated metrics, such as vulnerabilities and license compliance, without having to open each subproject individually.
56 +After creating a DevOps project in the portal, a Dependency-Track project is automatically created. The type of the new project is** Collection Project**. Subprojects which keep the real SBOM scan results are later created as children of this collection project. This makes it easier to see aggregated metrics, such as vulnerabilities and license compliance, without having to open each subproject individually.
57 +
57 57  For more details, see the [[Collection Projects>>https://docs.dependencytrack.org/usage/collection-projects/]] section in the Dependency-Track documentation.
58 58  
59 59  == Integration with Jenkins ==
... ... @@ -62,13 +62,11 @@
62 62  
63 63  [[image:1756907509490-678.png]]
64 64  
65 -A new Dependency-Track sub project is automatically created on the fly.
66 +A new Dependency-Track sub project is automatically created on the fly.
66 66  
67 67  Currently, this option is only available for Maven projects.
68 68  
69 69  
70 -== ==
71 -
72 72  = Users and Roles =
73 73  
74 74  * Projects, users and their roles in projects are managed in the DevOps Portal, the corresponding functions in Dependency-Track are disabled (UI and API)