This documentation is for a release that is no longer maintained
See documentation for the latest supported version 3 or the latest supported version 4.이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Chapter 24. Configuring Pipeline Execution
24.1. Overview 링크 복사링크가 클립보드에 복사되었습니다!
The first time a user creates a build configuration using the Pipeline build strategy, OpenShift Container Platform looks for the a template named jenkins-ephemeral
in the openshift
namespace and instantiates it within the user’s project. The jenkins-ephemeral
template that ships with OpenShift Container Platform creates, upon instantiation:
- a deployment configuration for Jenkins using the official OpenShift Container Platform Jenkins image
- a service and route for accessing the Jenkins deployment
- a new Jenkins service account
- rolebindings to grant the service account edit access to the project
Cluster administrators can control what is created by either modifying the content of the built-in template, or by editing the cluster configuration to direct the cluster to a different template location.
To modify the content of the default template:
oc edit template jenkins-ephemeral -n openshift
$ oc edit template jenkins-ephemeral -n openshift
To use a different template, such as the jenkins-persistent
template which uses persistent storage for Jenkins, add the following to your master configuration file:
- 1
- Defaults to
false
. Iffalse
, then no template will be instantiated. - 2
- Namespace containing the template to be instantiated.
- 3
- Name of the template to be instantiated.
- 4
- Name of the service to be created by the template upon instantiation.
- 5
- Optional values to pass to the template during instantiation.
When a Pipeline build configuration is created, OpenShift Container Platform instantiates the jenkinsPipelineConfig
template only if no existing service name in the project matches the serviceName
field. This means serviceName
must be chosen such that it is unique in the project.