Changes for page Dependency-Track

Summary

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

Details

Page properties

Content

...	...	@@ -16,8 +16,6 @@
16	16
17	17	[[Impact Analysis>>https://docs.dependencytrack.org/usage/impact-analysis/]]
18	18
19		-[[Collection-projects>>https://docs.dependencytrack.org/usage/collection-projects/]]
20		-
21	21	= Accessing Dependency-Track =
22	22
23	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.
...	...	@@ -56,7 +56,7 @@
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 =
	57	+= Projects =
60	60
61	61	== Dependency-Track Jenkins Integration ==
62	62
...	...	@@ -63,9 +63,10 @@
63	63	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.
64	64
65	65
66		-== Collection Project und Unterprojekte ==
	64	+== Collection Project ==
67	67
68	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	+For more details, see the [[Collection Projects>>https://docs.dependencytrack.org/usage/collection-projects/]] section in the Dependency-Track documentation.
69	69
70	70	= Users and Roles =
71	71