Changes for page Jenkins Shared Library

Last modified by Boris Folgmann on 2026/03/30 10:13

From version 11.2
edited by Boris Folgmann
on 2026/03/30 10:00
Change comment: There is no comment for this version
To version 12.1
edited by Boris Folgmann
on 2026/03/30 10:13
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -318,28 +318,24 @@
318 318  |(((
319 319  helmRegistry
320 320  )))|(((
321 -Helm registry of your DOaaS instance, which is usally 'https:~/~/registry-CUSTOMER.devops.t-systems.net/chartrepo/PROJECTKEY'
321 +Helm registry of your DOaaS instance, which is usually 'oci:~/~/registry-CUSTOMER.devops.t-systems.net/'
322 322  )))|(((
323 -Helm registry to which the packaged Helm chart is uploaded.
323 +Helm registry from which dependencies are download and 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 +were supported. If you pass now an URL like this, it will now throw an error.
326 326  )))
327 327  |(((
328 328  helmRegistryCredentialsId
329 329  )))|(((
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 +'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 acccessing Helm charts.
333 +Id of the Jenkins Credentials which have to be used to authenticate to the Helm registry for accessing Helm charts.
333 333  )))
334 -|= |pullHelmRegistry|
335 -Defaults to the Helm registry of your DevOps-as-a-Service instance which is usally 'oci:~/~/registry-CUSTOMER.devops.t-systems.net/'|
336 -|= |pullHelmRegistryCredentialsId|Id of the Jenkins Credentials which have to be used to authenticate to the pull Helm registry for pulling Helm charts.
337 - Defaults to helmRegistryCredentialsId|
338 -|= |pushHelmRegistry| Helm registry to which your chart is pushed.
339 - Defaults to the Helm registry of your DevOps-as-a-Service instance
340 - which is usally 'oci:~/~/registry-CUSTOMER.devops.t-systems.net/'|
341 -|= |pushHelmRegistryCredentialsId| Id of the Jenkins Credentials which have to be used to authenticate to the push Helm registry for pushing Helm charts.
342 - Defaults to helmRegistryCredentialsId|
335 +|= |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.
336 +|= |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.
337 +|= |pushHelmRegistry|Defaults to the Helm registry of your DevOps-as-a-Service instance which is usually 'oci:~/~/registry-CUSTOMER.devops.t-systems.net/'|Helm registry to which your chart is pushed.
338 +|= |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.
343 343  |=(% rowspan="4" %)(((
344 344  Container image signature
345 345  )))|(((