Skip to Content

Changes for page Dependency-Track

Last modified by Milad Afshar-Jahanshahi on 2025/09/03 14:31
From version 53.7
edited by Boris Folgmann
on 2025/09/03 14:23
Change comment: There is no comment for this version
To version 52.1
edited by Milad Afshar-Jahanshahi
on 2025/09/03 14:10
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Dependency Track
1 +Dependency-Track
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.borisfolgmannt-systemscom
1 +xwiki:XWiki.miladafshar-jahanshahit-systemscom
Content
... ... @@ -48,26 +48,23 @@
48 48  You can also access Dependency-Track directly using the following link format:
49 49  [[https:~~/~~/deptrack-<customer~>.devops.t-systems.net/projects>>https://<customer>.devops.t-systems.net/xwiki/wiki/<pkey>/view]] where <customer> is the id of your DevOps-as-a-Service instance.
50 50  
51 -If you are not already logged in to another tool in the tool chain or the DevOps portal, then you have to log in using your configured SSO credentials.
51 +If you are not already logged in to another tool in the toolchain or the DevOps portal, then you have to login using your configured SSO credentials.
52 52  
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** 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.
56 +After creating a DevOps project in the portal, a Dependency-Track project is automatically created.
57 57  
58 -For more details, see the [[Collection Projects>>https://docs.dependencytrack.org/usage/collection-projects/]] section in the Dependency-Track documentation.
58 +== Dependency-Track Jenkins Integration ==
59 59  
60 -== Integration with Jenkins ==
60 +When using sdcPipeline(), Maven projects automatically generate a Software Bill of Materials (SBOM) and are pushed to Dependency-Track project. This process is fully automated through the provided pipeline library. Currently, this option is only available for Maven projects.
61 61  
62 -The [[Jenkins Shared Library>>url:https://prd.sdc.t-systems.net/xwiki/wiki/devopsaas/view/Jenkins/Jenkins%20Shared%20Library/]] will automatically create SBOM (Software Bill of Materials) files for maven projects and upload them to Dependency-Track.
63 63  
64 -[[image:1756907509490-678.png]]
63 +== Collection Project ==
65 65  
66 -A new Dependency-Track sub project is automatically created on the fly.
65 +In Dependency-Track, these Maven builds are organized under a **Collection Project**. Subprojects (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.
66 +For more details, see the [[Collection Projects>>https://docs.dependencytrack.org/usage/collection-projects/]] section in the Dependency-Track documentation.
67 67  
68 -Currently, this option is only available for Maven projects.
69 -
70 -
71 71  = Users and Roles =
72 72  
73 73  * Projects, users and their roles in projects are managed in the DevOps Portal, the corresponding functions in Dependency-Track are disabled (UI and API)
... ... @@ -78,8 +78,8 @@
78 78  Projects in the DevOps portal are mapped to the corresponding project in Dependency-Track.
79 79  )))
80 80  
81 -* Users assigned to a project in the DevOps Portal are automatically added to the matching Dependency-Track projects with the roles as shown below: 
82 -** Role map(((
78 +* When Dependency-Track is added as a tool to an existing or new project, a corresponding Dependency-Track project is automatically created. Users assigned to the project in the DevOps Portal are then added to it with the roles defined in the configuration: 
79 +** Role mapping: (((
83 83  |=Project Role in DevOps Portal|=Permissions in Dependency-Track
84 84  |Admin|POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
85 85  |Master|(% colspan="1" %)POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
1756907509490-678.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.borisfolgmannt-systemscom
Size
... ... @@ -1,1 +1,0 @@
1 -5.4 KB
Content
© 2018-2025 T-Systems International GmbH