On 24.08.2015 15:44, Harrison Ripps wrote:
>
>
> On Mon, Aug 24, 2015 at 9:27 AM, Stef Walter <stefw(a)redhat.com
> <mailto:stefw@redhat.com>> wrote:
>
> On 24.08.2015 15 <tel:24.08.2015%2015>:15, Harrison Ripps wrote:
> >
> > On Mon, Aug 24, 2015 at 8:45 AM, Stef Walter <stefw(a)redhat.com
<mailto:stefw@redhat.com>
> > <mailto:stefw@redhat.com <mailto:stefw@redhat.com>>> wrote:
> >
> > On 24.08.2015 09 <tel:24.08.2015%2009>
> <tel:24.08.2015%2009>:03, Stef Walter wrote:
> > > On 24.08.2015 08 <tel:24.08.2015%2008>
> <tel:24.08.2015%2008>:54, Marius Vollmer wrote:
> > >> Peter <petervo(a)redhat.com
<mailto:petervo@redhat.com>
> <mailto:petervo@redhat.com <mailto:petervo@redhat.com>>> writes:
> > >>
> > >>> PROS:
> > >>>
> > >>> - It works and uses a newer OS (Ubuntu 14)
> > >>> - Allows you to ssh into instances to run / debug tests.
> > >>
> > >> This is very, very nice.
> > >>
> > >>> CONS:
> > >
> > > Obviously another big con is that this stuff is not Open
Source. These
> > > are proprietary services. But so is GitHub. But until we
have more
> > > resources, and/or an open source hosted CI service ... we'll
probably
> > > have to ignore this con.
> >
> > I was wrong about Travis. Travis is Open Source. Yay. Good for
them.
> > That changes how much effort I feel we should dedicate to
helping make
> > it work, filing bugs, etc.
> >
> > A little bird also whispered in my ear that Marius has found a
> > work-around for the Travis bug that has been bothering us.
> >
> >
> > Not sure if this would help, but the AOS team has a Jenkins server
where
> > we could do some more sophisticated CI testing:
> >
> >
https://ci.openshift.redhat.com/jenkins/
> >
> > I am one of the maintainers so I'd be happy to help set things up
if
> > this was of interest.
>
> Interesting. Have you migrated anything from Travis to that Jenkins
> instance? What did the process end up looking like?
>
>
> I have not done a Travis to Jenkins migration. However, based on looking
> at a reference Travis config[1], I'd say the porting is relatively
> painless. The Jenkins host needs to have the right tools installed on it
> and then you write a shell script for Jenkins to run.
>
> [1]:
https://github.com/openshift/origin/blob/master/.travis.yml
>
>
> But this is actually more interesting for the workloads we don't run
on
> Travis ... our integration tests ... which launch tons of VMs within
the
> space of a few minutes. Is that the sort of thing your Jenkins
instance
> can run? ie: nested virtualization, and/or root access etc?
>
>
> The public AOS Jenkins system is running on an EC2 instance. With its
> current workload, I don't think it has enough power to stand up a bunch
> of locally hosted VMs for testing. However, if the tests could be
> modified to spin up EC2 instances, or instances on the Red Hat public
> OpenStack cluster, then the AOS Jenkins host could certainly handle the
> workload of firing them up, running tests, and reporting on the test
> results.
True, but we snapshot images, and then spin up VMs, and do a test and
shutdown each within 10 seconds or so. For day to day use (vetting pull
requests) it makes sense to stay on some performant hardware.
Understood. I may still be able to help with this one. I'll follow up after
I've had a chance to talk to our ops team.
Stef
_______________________________________________
cockpit-devel mailing list
cockpit-devel(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cockpit-devel