On Mon, Jul 23, 2018 at 7:42 PM Alex Harui <aha...@adobe.com.invalid> wrote:
> Hi Greg, > > Thanks for the background. I assume that adding more disk space is > cost-prohibitive? > Most of our Jenkins nodes are donated to us, so we want to use their generous contributions as best we can. What would happen if builds.a.o went away and projects had to request and > use a VM with their own Jenkins instance? > Generally, projects can only request a single VM. I suspect that most projects want to burst-build across a few Jenkins nodes, and a single VM would serialize their builds/testing too much. There are likely some economies of scale in how we run our single Jenkins Master and a multitude of slave nodes. I'm not educated enough on Jenkins to really speak to this, however. Requesting more than a single VM *is* doable, but requires Board approval for the budget or a matching donation. (there may be more paths to multiple VMs, but those are the two recent approaches over the past month for Fineract and OpenWhisk to get more VMs) IIRC, the issue for my projects might be that VMs are currently only > available as Linux, not Windows? We can provide Windows VMs, no problem. Ubuntu 16.04, or Windows (not sure which release). And there is some special way that Jenkins can publish to Maven Snapshots > that would need to be replicated to the VM? > This gets trickier, sharing the necessary secrets for publishing. I'll leave that to Gavin, et al, to discuss. Cheers, -g
