Changes for page Build Options with Managed Jenkins Hosts
Last modified by DOaaS Operator on 2025/11/11 09:12
To version 2.1
edited by DOaaS Operator
on 2025/11/11 09:12
on 2025/11/11 09:12
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -14,7 +14,7 @@ 14 14 15 15 === Node Label 'docker' === 16 16 17 -Use this label in your Jenkinsfile node declaration to let the job run on the classic host based Jenkins agent. This is a Linux agent host, permanently available to the Jenkins master, equipped with preinstalled tools like Docker, kubectl, helm, etc. Tools provided by Jenkins plugins like e.g. maven are also available. To learn how to use these tools, see [[https:~~/~~/prd.sdc.t-systems.net/xwiki/ bin/view/Jenkins/Jenkinsfile#Jenkinsfile-Buildingwithtoolplug-ins>>https://prd.sdc.t-systems.net/xwiki/bin/view/Jenkins/Jenkinsfile#Jenkinsfile-Buildingwithtoolplug-ins]]. Please note that since the agent is shared for all builds, Docker images, Docker containers, workspaces and caches are accessible by all projects configured in the DevOps-as-a-Service instance. To reduce the visibility, clean your workspace after the build. The advantage of this host is the high speed of the build pipelines, since caches provide existing data on the next build run.17 +Use this label in your Jenkinsfile node declaration to let the job run on the classic host based Jenkins agent. This is a Linux agent host, permanently available to the Jenkins master, equipped with preinstalled tools like Docker, kubectl, helm, etc. Tools provided by Jenkins plugins like e.g. maven are also available. To learn how to use these tools, see [[https:~~/~~/prd.sdc.t-systems.net/xwiki/wiki/devopsaas/view/Jenkins/Jenkinsfile/#HBuildingwithtoolplug-ins>>https://prd.sdc.t-systems.net/xwiki/wiki/devopsaas/view/Jenkins/Jenkinsfile/#HBuildingwithtoolplug-ins]]. Please note that since the agent is shared for all builds, Docker images, Docker containers, workspaces and caches are accessible by all projects configured in the DevOps-as-a-Service instance. To reduce the visibility, clean your workspace after the build. The advantage of this host is the high speed of the build pipelines, since caches provide existing data on the next build run. 18 18 19 19 === Node Label 'dind' === 20 20