[Ci-users] openshift env for CI

Fri Mar 3 21:40:33 UTC 2017
Ari LiVigni <ari at redhat.com>

On Fri, Mar 3, 2017 at 3:11 PM, Colin Walters <walters at verbum.org> wrote:

> On Fri, Mar 3, 2017, at 02:49 PM, Brian Stinson wrote:
> > This is still in the bringup stage.
> Is it on baremetal?  This would make it easier to do virt-in-containers.
> If you recall I use Duffy to allocate worker machines which may do
> builds/tests, but not necessarily *on* or for the base CentOS 7 host.
> (BTW, I'd still like Atomic Host as a provisioning option)
> I've been thinking about changing this to set up an OpenShift cluster
> and have the jobs schedule containers into it...but the awkward thing
> about this (in thought experiment stage, not getting into things like
> networking across nodes)
> would be the duffy timeout killing the masters.
> > I think this scenario is about to become "painful" (we knew/know this is
> > coming). The reason for a single master was that the Jenkins frontend
> > was meant to be the point of collaboration to visualize the 'matrix' of
> > tests between related projects but lately it's more noisy than anything.
> Yeah.  I really don't like any of the Jenkins web UI to be honest, though
> the "blue ocean" stuff for Pipeline looks decent.  But that's more of
> a targeted specific case.

I think the Openshift/Jenkins/Jenkins Pipeline is the long term goal and
whether you use the Openshift or Jenkins Blue Ocean UI doesn't matter since
the information is presented in both.

> _______________________________________________
> Ci-users mailing list
> Ci-users at centos.org
> https://lists.centos.org/mailman/listinfo/ci-users

-== @ri ==-
My PGP fingerprint is F87F1EE7CD8BEE13
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/ci-users/attachments/20170303/0d9328d9/attachment-0003.html>