Changes for page Jenkins Shared Library

Summary

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

Details

Page properties

Content

...	...	@@ -329,12 +329,8 @@
329	329	)))|(((
330	330	'doaas-PROJECTKEY+jenkins-push-harbor' or 'PROJECTKEY-jenkins' (which were added to the credentials of your project folder in Jenkins when the project was set up by the DevOps Portal. While the first is added for Harbor, the second is added for Nexus OSS. That means that the library will automatically choose the best default for you. Please note that Harbor will be prefered, if both tools are used in the project.)
331	331	)))|(((
332		-Id of the Jenkins Credentials which have to be used to authenticate to the Helm registry for accessing Helm charts.
	332	+Id of the Jenkins Credentials which have to be used to authenticate to the Helm registry for acccessing Helm charts.
333	333	)))
334		-|= |pullHelmRegistry|Helm registry of your DevOps-as-a-Service instance which is usually 'oci:~/~/registry-CUSTOMER.devops.t-systems.net/'|Helm registry from which dependencies referenced in your chart are pulled.
335		-|= |pullHelmRegistryCredentialsId|the value set by helmRegistryCredentialsId|Id of the Jenkins Credentials which have to be used to authenticate to the pull Helm registry for pulling Helm charts.
336		-|= |pushHelmRegistry|Defaults to the Helm registry of your DevOps-as-a-Service instance which is usally 'oci:~/~/registry-CUSTOMER.devops.t-systems.net/'|Helm registry to which your chart is pushed.
337		-|= |pushHelmRegistryCredentialsId|the value set by helmRegistryCredentialsId|Id of the Jenkins Credentials which have to be used to authenticate to the push Helm registry for pushing Helm charts.
338	338	|=(% rowspan="4" %)(((
339	339	Container image signature
340	340	)))|(((