Changes for page Jenkins Shared Library

Summary

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

Details

Page properties

Content

...	...	@@ -39,7 +39,7 @@
39	39	11. **Docker**: this will also work for projects which are neither maven, nodejs or go. A Dockerfile is enough to trigger this part of the pipeline.
40	40	111. **Build Container Image**: If a Dockerfile is found a docker image is built.
41	41	111. **Test Container Image**: The image is started as an isolated container on the Jenkins agent. Any loglines written to stdout or stderr by the container will be displayed.A smoke test is performed which is a simple query for a valid answer on the exposed port of the container.
42		-111. **Push Container Image**: If the smoke test was successful the container image will be pushed to the image registry.
	42	+111. **Push Container Image**: If the smoke test was successful and the build was not done for a pull request the docker image will be pushed to the docker registry.
43	43	For easy identification of the image 3 image tags are defined:
44	44	1111. BRANCH_NAME-BUILD_NUMBER (e.g. 'production-1014')
45	45	1111. BRANCH_NAME-GIT_HASH (e.g. 'develop-8a7c4f2')
...	...	@@ -318,24 +318,19 @@
318	318	|(((
319	319	helmRegistry
320	320	)))|(((
321		-Helm registry of your DOaaS instance, which is usually 'oci:~/~/registry-CUSTOMER.devops.t-systems.net/'
	321	+Helm registry of your DOaaS instance, which is usally 'https:~/~/registry-CUSTOMER.devops.t-systems.net/chartrepo/PROJECTKEY'
322	322	)))|(((
323		-Helm registry from which dependencies are download and to which the packaged Helm chart is uploaded.
	323	+Helm registry to which the packaged Helm chart is uploaded.
324	324
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.
	325	+
327	327	)))
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.)
	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.)
332	332	)))|(((
333		-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.
334	334	)))
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.
339	339	|=(% rowspan="4" %)(((
340	340	Container image signature
341	341	)))|(((