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

Slide slide.o.mix at gmail.com
Tue Feb 18 02:55:41 UTC 2020


I do have a working Windows Nanoserver ACI agent now for Windows builds. I
have been testing it with one of the plugins I maintain. If we could switch
to ACI agents completely, that would save quite a bit of money wouldn't it?

On Mon, Feb 17, 2020 at 1:57 AM Baptiste Mathus <bmathus at cloudbees.com>
wrote:

> See inline
>
> On Sat, Feb 8, 2020 at 1:10 AM R. Tyler Croy <rtyler at brokenco.de> wrote:
>
>> (replies inline)
>>
>
> [snip]
>
>
>> I agree, the same-ness of our hosts in Azure right now is especially
>> useful.
>> Other than using Puppet, like we have with fixed agents in the past, I
>> don't
>> have a great solution in mind for how the sameness could be acheived by
>> fixed
>> and cloud-based agents simultaneously.
>>
>
> In my past, in a fixed environment where getting VMs was a manual process,
> we achieved this by using Docker Swarm (v1) to balance the load
> transparently to all VMs + agents running in Docker.
> This was working great for ~60 hours of builds per day (so, might not work
> for the likely hundreds of hours per day on ci.jenkins.io).
>
> Nowadays, given Docker Swarm is deprecated, my guess is that it would be
> K8S? (though I'd hope we do not need to adapt Jenkinsfile and the way we
> build... ?)
>
> -- Baptiste
>
>
> _______________________________________________
> Jenkins-infra mailing list
> Jenkins-infra at lists.jenkins-ci.org
> http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra
>


-- 
Website: http://earl-of-code.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20200217/5d8da50b/attachment.html>


More information about the Jenkins-infra mailing list