Commit 97699a80 authored by João Lino's avatar João Lino

Switched docker agent for a docker template and enabled the configuration as...

Switched docker agent for a docker template and enabled the configuration as code option for it to be configured.
parent d9b1c09c
......@@ -311,10 +311,13 @@ master:
# become the content of the configuration yaml file. The first line after this is a JCasC root element, eg jenkins, credentials,
# etc. Best reference is https://<jenkins_url>/configuration-as-code/reference. The example below creates a welcome message:
JCasC:
enabled: false
defaultConfig: false
enabled: true
defaultConfig: true
pluginVersion: "1.36"
configScripts: {}
configScripts:
welcome-message: |
jenkins:
systemMessage: Welcome to joaolino.com demo CI\CD server. This Jenkins is configured and managed 'as code'.
# welcome-message: |
# jenkins:
# systemMessage: Welcome to our CI\CD server. This Jenkins is configured and managed 'as code'.
......@@ -539,7 +542,11 @@ agent:
# master.JCasC.enabled: true
# master.JCasC.defaultConfig: true
# Best reference is https://<jenkins_url>/configuration-as-code/reference#Cloud-kubernetes. The example below creates a python pod template.
podTemplates: {}
podTemplates:
docker: |
- name: docker
label: jenkins-docker
serviceAccount: jenkins
# python: |
# - name: python
# label: jenkins-python
......@@ -558,10 +565,7 @@ agent:
# Here you can add additional agents
# They inherit all values from `agent` so you only need to specify values which differ
additionalAgents:
docker:
podName: docker
customJenkinsLabels: docker
additionalAgents: {}
# maven:
# podName: maven
# customJenkinsLabels: maven
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment