I don't mind at all :-)

Erik

Den lørdag 1. august 2015 skrev Pierre-Luc Dion <pd...@cloudops.com>
følgende:

> Hi Erik,
> Do you think we could repurpose your slave, as docker build slave? do you
> mind if we had the host in the Chef-Server, I'll create you an account,  I
> setup some roles for jenkins slaves, all cookbooks are in:
> https://github.com/CloudStack-extras/ci-chefrepo
>
> Docker would need to be updated for at least version 1.6.x
>
> For the  fastbuildserver, I've tested the pytest branch against master, but
> it wasn't working because marvin and tests changed too much. what I saw
> from pytest is that the output of it is much more understandable, clear and
> usable the marvins one.  I'll disable the job for now.
>
>
> Cheers,
>
>
>
> On Mon, Jul 27, 2015 at 11:23 PM, Erik Weber <terbol...@gmail.com
> <javascript:;>> wrote:
>
> > for item 4 i think you are right. When the old fastbuildserver went
> offline
> > i provided a new host, but never knew the job, but i have been meaning to
> > ask if it should test master and not its own stale branch
> >
> > Erik
> >
> > Den tirsdag 28. juli 2015 skrev Pierre-Luc Dion <pdion...@apache.org
> <javascript:;>>
> > følgende:
> >
> > > Hi,
> > >
> > > I've spend some times understanding Jenkins job on j.bac.o and it look
> > like
> > > there is few job that should be removed and pause? Maybe persons aware
> of
> > > them can answer?
> > >
> > > 1. There is 2 build-master-slowbuild
> > > <http://jenkins.buildacloud.org/job/build-master-slowbuild/> running
> > every
> > > 3hours , this job take ~2h, does just 1 would be enough?
> > > 2. We start to have failed/offline slave, who have access to them to
> fix
> > > them?
> > >     *  cloudstack-buildslave-static-001
> > >    * fastbuildserver
> > >    * linodebuildserver
> > >    * rpmbuilder-2
> > >    * systemvmbuilder
> > > 3. view: cloudstack-qa-master   half jobs are in RED
> > > 4. fastsimulatorbuild:  I think this job use a old branch, not even
> > testing
> > > master ?
> > > 5. do we drop jobs for 4.3 ?
> > >
> > >
> > > Thanks
> > >
> > > PL
> > >
> >
>

Reply via email to