Skip to Content

Changes for page Dependency-Track

Last modified by Milad Afshar-Jahanshahi on 2025/09/03 14:31
From version 51.1
edited by Milad Afshar-Jahanshahi
on 2025/09/03 14:07
Change comment: There is no comment for this version
To version 53.3
edited by Boris Folgmann
on 2025/09/03 14:15
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.miladafshar-jahanshahit-systemscom
1 +xwiki:XWiki.borisfolgmannt-systemscom
Content
... ... @@ -27,7 +27,7 @@
27 27  Unlike other tools, login is only possible if the user has a valid license and is assigned a role in at least one Dependency-Track project.
28 28  )))
29 29  
30 -After completing the preconditions, a project in Dependency-Track, which is part of the DevOps-as-a-Service toolchain, can be accessed via the DevOps Portal or directly through a URL.
30 +After completing the preconditions, a project in Dependency-Track, which is part of the DevOps-as-a-Service tool chain, can be accessed via the DevOps Portal or directly through the Depdency-Track URL.
31 31  
32 32  == Via DevOps Portal ==
33 33  
... ... @@ -38,9 +38,9 @@
38 38  (% class="box warningmessage" %)
39 39  (((
40 40  ⚠ **Note**
41 -If you are still unable to access your project in Dependency-Track, it may be because you are logged in with an old session that still uses outdated permissions or To resolve this issue, please log out and then log in again. 
42 -For some reason, you may need to click more than one option in OpenID or trigger the login section ([[https:~~/~~/deptrack-<customer~>.devops.t-systems.net/>>https://<customer>.devops.t-systems.net/xwiki/wiki/<pkey>/view]]login) to access the new session.
43 -\\[[image:login1.png||alt="Untitled2.png" height="250" width="600"]]
41 +If you are still unable to access your project in Dependency-Track, it may be because you are logged in with an old session that still uses outdated permissions. To resolve this issue, please log out and then log in again. 
42 +For some reason, you may need to click more than one time on the OpenID button or go to the login page ([[https:~~/~~/deptrack-<customer~>.devops.t-systems.net/>>https://<customer>.devops.t-systems.net/xwiki/wiki/<pkey>/view]]login) to access the new session.
43 +\\[[image:login1.png||alt="Untitled2.png" data-xwiki-image-style-border="true" height="297" width="650"]]
44 44  )))
45 45  
46 46  == Via Direct URL ==
... ... @@ -48,7 +48,7 @@
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 toolchain or the DevOps portal, then you have to login using your configured SSO credentials.
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.
52 52  
53 53  
54 54  = Projects =
... ... @@ -57,9 +57,13 @@
57 57  
58 58  == Dependency-Track Jenkins Integration ==
59 59  
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.
60 +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.
61 61  
62 +[[image:1756907509490-678.png]]
62 62  
64 +A new Dependency-Track sub project is automatically created on the fly. Currently, this option is only available for Maven projects.
65 +
66 +
63 63  == Collection Project ==
64 64  
65 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.
1756907509490-678.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.borisfolgmannt-systemscom
Size
... ... @@ -1,0 +1,1 @@
1 +5.4 KB
Content
XWiki.XWikiComments[0]
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.miladafshar-jahanshahit-systemscom
Comment
... ... @@ -1,13 +1,0 @@
1 -[[https:~~/~~/docs.dependencytrack.org/>>url:https://docs.dependencytrack.org/]]
2 -
3 -Optionales Tool: aktivieren als Project Admin für das Projekt, zuweisen von Lizenzen als Portal Admin an die entsprechenden User
4 -
5 -Im Gegensatz zu anderen Tools ist ein Login nur dann möglich, wenn der User eine Lizenz hat und in mindestens einem DepTrack Projekt eine Rolle hat  ~-~-> Done
6 -
7 -Dashboard -> DepTrack Login Seite  ~-~-> DOne
8 -
9 -Pilotkunden Preview ist
10 -
11 -Nur sdcPipeline() wird unterstützt, nur maven (bisher), alles automatisch
12 -
13 -Collection Project und Unterprojekte
Date
... ... @@ -1,1 +1,0 @@
1 -2025-09-03 08:45:10.589
© 2018-2025 T-Systems International GmbH