The goal is to add to ci.jenkins.io the same workload capability as ACI agents provides but with Kubernetes agents.
INFRA-2919: Kubernetes is configured with an AWS EKS cluster
- Why? ACI cost a kidney, and are a liability. Merging workloads to a static Kube cluster would allow a static build capability to decrease the infra cost, and keeping ACI for "peaks" in the build queue
This changes leads to the depreciation of the attribute useAci for the pipeline library function `buildPlugin()` (see PR on the library at https://github.com/jenkins-infra/pipeline-library/pull/220).
If you land on this page because of a deprecation message: please edit the file Jenkinsfile at the root of your repository and replace the atrribute useAci by useContainerAgent.
- It's only a name change: there are no functionnal changes.
- You can find an example change on the following pull request: https://github.com/jenkinsci/jenkins-infra-test-plugin/pull/12