[Jenkins-infra] A random thought for reducing ci.j.io cost

Jesse Glick jglick at cloudbees.com
Fri Feb 7 21:58:32 UTC 2020


On Fri, Feb 7, 2020 at 4:22 PM R. Tyler Croy <rtyler at brokenco.de> wrote:
> The downsides that come to mind

>From the developer perspective, the obvious downside would be the
likelihood that these machines would behave subtly differently from
dynamically provisioned cloud machines / containers, leading to
hard-to-diagnose occasional build failures. It is more attractive to
have a homogeneous pool of agents provisioned from a cloud service,
especially if the provisioning configuration is “as code”.

I continue to think that the main issue as outlined in INFRA-1633 is
that we do way more builds than we really need, and that we could
easily change CI configuration to skip many of them without much
impact on workflow.


More information about the Jenkins-infra mailing list