Changes for page Dependency-Track

Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 1 added, 0 removed)
  • 1756907509490-678.png

Details

Page properties

Content

...	...	@@ -53,18 +53,21 @@
53	53
54	54	= Projects =
55	55
56		-After creating a DevOps project in the portal, a Dependency-Track project is automatically created.
	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.
57	57
58		-== Dependency-Track Jenkins Integration ==
	58	+For more details, see the [[Collection Projects>>https://docs.dependencytrack.org/usage/collection-projects/]] section in the Dependency-Track documentation.
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	+== Integration with Jenkins ==
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.
62	62
63		-== Collection Project ==
	64	+[[image:1756907509490-678.png]]
64	64
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.
	66	+A new Dependency-Track sub project is automatically created on the fly.
67	67
	68	+Currently, this option is only available for Maven projects.
	69	+
	70	+
68	68	= Users and Roles =
69	69
70	70	* Projects, users and their roles in projects are managed in the DevOps Portal, the corresponding functions in Dependency-Track are disabled (UI and API)
...	...	@@ -75,8 +75,8 @@
75	75	Projects in the DevOps portal are mapped to the corresponding project in Dependency-Track.
76	76	)))
77	77
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: (((
	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(((
80	80	|=Project Role in DevOps Portal|=Permissions in Dependency-Track
81	81	|Admin|POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
82	82	|Master|(% colspan="1" %)POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS

1756907509490-678.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+xwiki:XWiki.borisfolgmannt-systemscom

Size

...	...	@@ -1,0 +1,1 @@
	1	+5.4 KB

Content