Changes for page Dependency-Track

Summary

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

Details

Page properties

Content

...	...	@@ -45,7 +45,7 @@
45	45
46	46	== Via Direct URL ==
47	47
48		-You can also access Dependency-Track directly using the following link format:
	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	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.
...	...	@@ -53,14 +53,16 @@
53	53
54	54	= Projects =
55	55
56		-== Dependency-Track Jenkins Integration ==
	56	+After creating a DevOps project in the portal, a Dependency Track project is automatically created.
57	57
58		-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.
	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	60
	62	+
61	61	== Collection Project ==
62	62
63		-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.
	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.
64	64	For more details, see the [[Collection Projects>>https://docs.dependencytrack.org/usage/collection-projects/]] section in the Dependency-Track documentation.
65	65
66	66	= Users and Roles =
...	...	@@ -70,7 +70,7 @@
70	70	(% class="box warningmessage" %)
71	71	(((
72	72	⚠ **Note**
73		-Projects in the DevOps portal are mapped to the corresponding teams in Dependency-Track.
	75	+Projects in the DevOps portal are mapped to the corresponding teams in Dependency-rack.
74	74	)))
75	75
76	76	* 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 :