Mailing-List: contact builds-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: builds@apache.org
Received-SPF: pass (nike.apache.org: domain of omuppi1@gmail.com designates
 209.85.212.174 as permitted sender)
MIME-Version: 1.0
Sender: omuppi1@gmail.com
In-Reply-To: 
 <CANyrgvexN=KsmdNgChhciuLpy7WawrSpba5m+PgDE9ueRcnxPg@mail.gmail.com>
References: <2447967.3AYf8FNZr7@herve-desktop>
	<CACK5iZe=Goa10a1g3pwFvmorBo34VqOkJjuc=4Gq9MsB1OkpzQ@mail.gmail.com>
	<CANyrgvexN=KsmdNgChhciuLpy7WawrSpba5m+PgDE9ueRcnxPg@mail.gmail.com>
Date: Mon, 31 Mar 2014 23:24:12 -0700
Message-ID: 
 <CACK5iZfyhDgzkEo5yTUPJf1G=WTAiKBKHRdN+o1sp0OFgtHWFg@mail.gmail.com>
Subject: Re: volunteering for ASF Jenkins farm service maintenance
From: OmPrakash Muppirala <bigosmallm@gmail.com>
To: "builds@apache org" <builds@apache.org>
Content-Type: multipart/alternative; boundary=bcaec53f35f571590904f5f537ea

--bcaec53f35f571590904f5f537ea
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Mar 31, 2014 11:15 PM, "Jake Farrell" <jfarrell@apache.org> wrote:
>
> Hey Om
> You are right, talk is cheap. being an admin on any one of the systems
that
> we run is more than maintaining your pet project and more about providing
> reliable systems for all of our projects to use. I'm sorry that your
> project is experiencing a problem with one of our systems. There is an
open
> issue for this currently, INFRA-7488, and it has been assigned and is
being
> worked on and it is understood that this is a pain point that needs to be
> addressed for Apache Flex. We appreciate your understanding as we work
> through all of the open issues that we face and if you are interested we
> are always looking for volunteers who are willing to step up and help.

I already volunteered to help.  I volunteer again.  How do I sign up?

Thanks,
Om

>
> Thanks again for your patience in this
> -Jake
>
>
>
>
> On Tue, Apr 1, 2014 at 1:06 AM, OmPrakash Muppirala <bigosmallm@gmail.com
>wrote:
>
> > Herv=E9,
> >
> > Thanks for bringing this issue up.  I second everything you said.
> >
> > Having a good build system is essential for a project's success.  I am
sure
> > the ASF realises this, which is why they have invested in all the
hardware
> > on which the build systems run.  But it is of really no use to us
because
> > there is no one around to actively maintain and provide support for it.
> >
> > I know that the admins are volunteers and that they have a real life as
> > well.  But, I am a volunteer too.  Every week I get only a few hours to
> > spare working on my choice of an open source project.  But I often have
to
> > end up trying to fix a broken build on a server on which I don't have
real
> > access to, that nobody wants to provide support.  No one responds to
> > emails.  There is very little reaction to JIRA tickets.
> >
> > Again, talk is cheap.  I am here to offer my time to fix the builds
issues
> > so that at least my project of choice (Apache Flex) benefits from it.
 If I
> > have additional time, I can help out with other build issues as well.
> >
> > What does it take to become an admin for Jenkins builds at the ASF?
 What
> > does it take for the current admins to take notice and realize that
this is
> > a real problem?
> >
> > Thanks,
> > Om
> >  On Mar 30, 2014 4:47 AM, "Herv=E9 BOUTEMY" <herve.boutemy@free.fr> wro=
te:
> >
> > > Hi,
> > >
> > > Like many people in ASF projects, I need a good CI service: Jenkins
is a
> > > good
> > > tool, then I expected ASF Jenkins farm to give a good service. That's
not
> > > the
> > > case for a few monthes (no pun intended).
> > >
> > > Then I'm trying to help by reporting problems, updating documentation
on
> > > wiki
> > > page, trying to answer to people on the list who face same problems
than
> > > me,
> > > ping people able to do something (trying not to upset them).
> > >
> > > From these monthes, I only saw few Jenkins admins working on problems=
,
> > > always
> > > the same 2 or 3 (not all on the wiki page). But they seem to have
little
> > > time
> > > to fix immediate issues. And I don't see any plan for fixing recurrin=
g
> > > problems,
> > > apart from master machine change in january: maybe I'm not on the
right
> > > list,
> > > maybe there is nothing done.
> > >
> > > I'm ready to give time on this service. But I need to know how to
engage
> > > with
> > > people interested in recurring problems, discuss plans to improve the
> > > service.
> > > Having admin rights on the farm can help, but without discussion with
the
> > > Jenkins farm admins team to decrypt problems and choose a concerted
> > > solution,
> > > that will only do half of a solution (better than nothing)
> > >
> > > Please let me know how to help to get a better service.
> > >
> > > Regards,
> > >
> > > Herv=E9
> > >
> >

--bcaec53f35f571590904f5f537ea--