Changes for page Dependency-Track
Last modified by Milad Afshar-Jahanshahi on 2025/09/03 14:31
From version 32.2
edited by Milad Afshar-Jahanshahi
on 2025/09/03 12:54
on 2025/09/03 12:54
Change comment:
There is no comment for this version
To version 35.1
edited by Milad Afshar-Jahanshahi
on 2025/09/03 13:01
on 2025/09/03 13:01
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -20,7 +20,7 @@ 20 20 21 21 = Accessing Dependency-Track = 22 22 23 -Dependency-Track is integrated into the DO AAStoolchain, but for now it’s only offered in the Pilotkunden Preview. To get started, a few prerequisites need to be in place.23 +Dependency-Track is integrated into the DevOps-as-a-Service toolchain, but for now it’s only offered in the Pilotkunden Preview. To get started, a few prerequisites need to be in place. 24 24 25 25 == Preconditions in DevOps portal to access Dependency-Track == 26 26 ... ... @@ -33,16 +33,6 @@ 33 33 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. 34 34 ))) 35 35 36 - 37 - 38 - 39 - 40 - 41 - 42 - 43 - 44 - 45 - 46 46 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. 47 47 48 48 == Via DevOps Portal == ... ... @@ -67,14 +67,14 @@ 67 67 68 68 69 69 70 -== Dependency-Track Jenkins Intera ction ==60 +== Dependency-Track Jenkins Integration == 71 71 72 - NursdcPipeline()wirdunterstützt,nurmaven(bisher),alles automatisch62 +When using sdcPipeline(), Maven projects automatically generate a Software Bill of Materials (SBOM) and are pushed to Dependency-Track. This process is fully automated through the provided pipeline library. Currently, this option is only available for Maven projects. 73 73 74 74 75 75 == Collection Project und Unterprojekte == 76 76 77 - TODO67 +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 collection. This makes it easier to see aggregated metrics, such as vulnerabilities and license compliance, without having to open each subproject individually. 78 78 79 79 = Users, Projects and Roles = 80 80