Changes for page Dependency-Track
Last modified by Milad Afshar-Jahanshahi on 2025/09/03 14:31
From version 36.1
edited by Milad Afshar-Jahanshahi
on 2025/09/03 13:02
on 2025/09/03 13:02
Change comment:
There is no comment for this version
To version 33.2
edited by Milad Afshar-Jahanshahi
on 2025/09/03 12:56
on 2025/09/03 12:56
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -56,18 +56,17 @@ 56 56 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. 57 57 58 58 59 -= Projects = 60 60 61 -== Dependency-Track Jenkins Inte gration ==60 +== Dependency-Track Jenkins Interaction == 62 62 63 - WhenusingsdcPipeline(),Maven projectsautomatically generate a Software Bill of Materials(SBOM) and are pushed to Dependency-Track.This process is fully automated through the provided pipelinelibrary. Currently,this option is onlyavailablefor Maven projects.62 +Nur sdcPipeline() wird unterstützt, nur maven (bisher), alles automatisch 64 64 65 65 66 66 == Collection Project und Unterprojekte == 67 67 68 - 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.67 +TODO 69 69 70 -= Users and Roles = 69 += Users, Projects and Roles = 71 71 72 72 * Projects, users and their roles in projects are managed in the DevOps Portal, the corresponding functions in Dependency-Track are disabled (UI and API) 73 73