Changes for page Jenkins Shared Library

Summary

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

Details

Page properties

Content

...	...	@@ -320,7 +320,7 @@
320	320	)))|(((
321	321	Helm registry of your DOaaS instance, which is usually 'oci:~/~/registry-CUSTOMER.devops.t-systems.net/'
322	322	)))|(((
323		-Helm registry from which dependencies are download and to which the packaged Helm chart is uploaded.
	323	+Helm registryfro to which the packaged Helm chart is uploaded.
324	324
325	325	In older versions of the library chart museum URLs like 'https:~/~/registry-CUSTOMER.devops.t-systems.net/chartrepo/PROJECTKEY'
326	326	were supported. If you pass now an URL like this, it will now throw an error.
...	...	@@ -328,7 +328,7 @@
328	328	|(((
329	329	helmRegistryCredentialsId
330	330	)))|(((
331		-'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	+ '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.)
332	332	)))|(((
333	333	Id of the Jenkins Credentials which have to be used to authenticate to the Helm registry for accessing Helm charts.
334	334	)))