Changes for page Dependency-Track

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -53,21 +53,22 @@
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 ==
61		-
62	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	64	[[image:1756907509490-678.png]]
65	65
66		-A new Dependency-Track sub project is automatically created on the fly.
	64	+A new Dependency-Track sub project is automatically created on the fly. Currently, this option is only available for Maven projects.
67	67
68		-Currently, this option is only available for Maven projects.
69	69
	67	+== Collection Project ==
70	70
	69	+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.
	70	+For more details, see the [[Collection Projects>>https://docs.dependencytrack.org/usage/collection-projects/]] section in the Dependency-Track documentation.
	71	+
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(((
	82	+* 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:
	83	+** 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