-
New Feature
-
Resolution: Unresolved
-
Minor
The ability to use a yamlFile is helpful to centralize templates across multiple teams, but it would be interesting if we can add more containers on top of the yamlFile-provided ones.
For example, yamlFiles.
Something like:
agent {
kubernetes {
yamlFiles(['path-to-global.yml', 'my-teams-containers.yml'])
yamlMergeStrategy merge()
}
}
[JENKINS-63679] Provide a way to pass multiple yamlFiles
Chadi El Masri
created issue -
Chadi El Masri
made changes -
| Description |
Original:
The ability to use a yamlFile is helpful to centralize templates across multiple teams, but it would be interesting if we can add more containers on top of the yamlFile-provided ones. For example, *yamlFiles*. Something like: {code:java} agent { kubernetes { yamlFiles(['path-to-global.yml', 'my-teams-containers.yml]) } } {code} |
New:
The ability to use a yamlFile is helpful to centralize templates across multiple teams, but it would be interesting if we can add more containers on top of the yamlFile-provided ones. For example, *yamlFiles*. Something like: {code:java} agent { kubernetes { yamlFiles(['path-to-global.yml', 'my-teams-containers.yml']) } } {code} |
Chadi El Masri
made changes -
| Description |
Original:
The ability to use a yamlFile is helpful to centralize templates across multiple teams, but it would be interesting if we can add more containers on top of the yamlFile-provided ones. For example, *yamlFiles*. Something like: {code:java} agent { kubernetes { yamlFiles(['path-to-global.yml', 'my-teams-containers.yml']) } } {code} |
New:
The ability to use a yamlFile is helpful to centralize templates across multiple teams, but it would be interesting if we can add more containers on top of the yamlFile-provided ones. For example, *yamlFiles*. Something like: {code:java} agent { kubernetes { yamlFiles(['path-to-global.yml', 'my-teams-containers.yml']) yamlMergeStrategy merge() } } {code} |