Changes for page Dependency-Track

Summary

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

Details

Page properties

Content

...	...	@@ -20,10 +20,7 @@
20	20
21	21	= Accessing Dependency-Track =
22	22
23		-(% class="box warningmessage" %)
24		-(((
25		-In our toolchain, Dependency-Track is currently available only for Pilotkunden Preview.
26		-)))
	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.
27	27
28	28	== Preconditions in DevOps portal to access Dependency-Track ==
29	29
...	...	@@ -33,18 +33,9 @@
33	33	(% class="box warningmessage" %)
34	34	(((
35	35	⚠ **Note**
36		-Im Gegensatz zu anderen Tools ist ein Login nur dann möglich, wenn der User eine Lizenz hat und in mindestens einem DepTrack Projekt eine Rolle hat
	33	+Unlike other tools, login is only possible if the user has a valid license and is assigned a role in at least one Dependency-Track project.
37	37	)))
38	38
39		-
40		-
41		-
42		-
43		-
44		-
45		-
46		-
47		-
48	48	After completing the preconditions, a project in Dependency-Track, which is part of the DevOps-as-a-Service toolchain, can be accessed via the DevOps Portal or directly through a URL.
49	49
50	50	== Via DevOps Portal ==
...	...	@@ -69,9 +69,9 @@
69	69
70	70
71	71
72		-== Dependency-Track Jenkins Interaction ==
	60	+== Dependency-Track Jenkins Integration ==
73	73
74		-Nur sdcPipeline() wird unterstützt, nur maven (bisher), alles automatisch
	62	+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.
75	75
76	76
77	77	== Collection Project und Unterprojekte ==