Return-Path: <builds-return-3597-apmail-builds-archive=apache.org@apache.org>
X-Original-To: apmail-builds-archive@minotaur.apache.org
Delivered-To: apmail-builds-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id EFCF511ECE
	for <apmail-builds-archive@minotaur.apache.org>;
 Sat,  5 Apr 2014 20:05:28 +0000 (UTC)
Received: (qmail 54279 invoked by uid 500); 5 Apr 2014 20:05:24 -0000
Delivered-To: apmail-builds-archive@apache.org
Received: (qmail 54034 invoked by uid 500); 5 Apr 2014 20:05:21 -0000
Mailing-List: contact builds-help@apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:builds-help@apache.org>
List-Unsubscribe: <mailto:builds-unsubscribe@apache.org>
List-Post: <mailto:builds@apache.org>
List-Id: <builds.apache.org>
Reply-To: builds@apache.org
Delivered-To: mailing list builds@apache.org
Received: (qmail 54017 invoked by uid 99); 5 Apr 2014 20:05:18 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 05 Apr 2014 20:05:18 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=10
	tests=RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of robert.munteanu@gmail.com
 designates 209.85.160.182 as permitted sender)
Received: from [209.85.160.182] (HELO mail-yk0-f182.google.com)
 (209.85.160.182)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 05 Apr 2014 20:05:12 +0000
Received: by mail-yk0-f182.google.com with SMTP id 142so4204782ykq.27
        for <multiple recipients>; Sat, 05 Apr 2014 13:04:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:sender:in-reply-to:references:date:message-id:subject
         :from:to:cc:content-type:content-transfer-encoding;
        bh=K2pIGNq5F6jDY7j0w0/Oku8SHsTfqkA99eXvvOZRtoM=;
        b=oQME/uZaLwUbwZsm4oCW2A3HVWv0d0SNQqRY5swDC0UO5QP3TaPZFq+NJnYLlRcIfS
         1EcIEI6KFjfxLA9xbU7B+KP5JcVWMQmysXbOf3NBryd7rl36hq2AfjdhbgAkHKEKylyC
         xTOEYqFOg25Z8HR4MaFPlfQWVi1b9YXH9dIL8QxcQdsErtDH+jbp9IdSsQm0iIFEjEOE
         e2uM4guDbklU0COcvSOqXMDfHqAMN6E7ht3/TvJ8HU6Qf2j+N4XNLZd5ekhr+hHc9XwB
         Yh6+/NGElnfNqJtCfMQpJlrlQ9PdDtfN/09teXI0vqJuL0CJaTBkLdTjbMJb3m0eblfh
         SPCQ==
MIME-Version: 1.0
X-Received: by 10.236.141.242 with SMTP id g78mr29228002yhj.50.1396728290732;
 Sat, 05 Apr 2014 13:04:50 -0700 (PDT)
Sender: robert.munteanu@gmail.com
Received: by 10.170.72.213 with HTTP; Sat, 5 Apr 2014 13:04:50 -0700 (PDT)
In-Reply-To: 
 <CANyrgvc8w45C6Xu-mkk8L2tqJ3O3Kj57thxuo75vpJ7r9+bLew@mail.gmail.com>
References: <2447967.3AYf8FNZr7@herve-desktop>
	<CANyrgvdKczMr7uajpWt-oWtpDNYAj5Sz07iwhBTUUnrrSCfF2A@mail.gmail.com>
	<1718506.Aa2HWjKsZs@herve-desktop>
	<2334217.1dCUSzMDyD@herve-desktop>
	<CACK5iZdVv0yvk=xBXHHs9V5TpZ5VU4w4uAM71kiQr0np=zgv5A@mail.gmail.com>
	<CANyrgvc8w45C6Xu-mkk8L2tqJ3O3Kj57thxuo75vpJ7r9+bLew@mail.gmail.com>
Date: Sat, 5 Apr 2014 23:04:50 +0300
X-Google-Sender-Auth: 7GZMFAjo0RUL-B1gD4zCDj1fe6g
Message-ID: 
 <CAC8ULPZutBMaOKF0ofejXF9bvV87BnYQuWyGc5YLun+6348gMQ@mail.gmail.com>
Subject: Re: volunteering for ASF Jenkins farm service maintenance
From: Robert Munteanu <robert@lmn.ro>
To: builds@apache.org, jfarrell@apache.org
Cc: OmPrakash Muppirala <bigosmallm@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Virus-Checked: Checked by ClamAV on apache.org

On Thu, Apr 3, 2014 at 11:38 PM, Jake Farrell <jfarrell@apache.org> wrote:
> Om, Herve
> What action are you specifically trying to achieve with the role you are
> referring to as 'maintainer' ?

I know very little about how you manage the infrastructure, so this
might be very much off the mark, but bear with me :-)

The Wikimedia servers are completely configured throught puppet [1] .
They have also opened up the git repository, so that anyone can clone
it and submit patches if they desire, using their gerrit instance [2]
. This allows external contributors to easily make contributions to
the wikimedia infra, without ever needing OS-level access.

I _know_ it's not as easy as 'make it open' ; there are security
issues to consider and someone needs the time to review these
contributions. However, it would make it much easier for the
build/release engineers of Apache projects to contribute to infra.

Just my 2 cents.

Cheers,

Robert


[1]: https://blog.wikimedia.org/2011/09/19/ever-wondered-how-the-wikimedia-=
servers-are-configured/
[2]: https://gerrit.wikimedia.org/r/#/q/status:open+project:operations/pupp=
et,n,z

>
> With the jenkins-admin karma you have you are able to look at jenkins
> tickets that are in the infrastructure backlog and close them out or you
> can answering questions on the builds@ list that people have. Just like a=
ny
> other Apache project karma is earned and not just given. This is probably=
 a
> better link explaining how to volunteer than the wiki link for jenkins
>
> http://apache.org/dev/infra-volunteer.html#assist
>
> Your offer to help is truly appreciated, we are always looking for people
> to step up and help. We are happy to answer any questions you have, eithe=
r
> via this mailing list or you can find us on freenode in #asfinfra
>
> -Jake
>
>
>
> On Thu, Apr 3, 2014 at 3:08 PM, OmPrakash Muppirala <bigosmallm@gmail.com=
>wrote:
>
>> Jake,
>>
>> Just to be clear, we want to get a 'maintainer' account so we can help o=
ut
>> with maintaining Jenkins.
>> I already have an 'Admin' account, but I can only do limited things via
>> the web console.
>>
>> The FAQ page you mentioned does not have this information.
>>
>> Thanks,
>> Om
>>
>>
>> On Thu, Apr 3, 2014 at 10:24 AM, Herv=C3=A9 BOUTEMY <herve.boutemy@free.=
fr>wrote:
>>
>>> > >  thanks again for volunteering, appreciate the help
>>> was this an april's fool?
>>>
>>> Regards,
>>>
>>> Herv=C3=A9
>>>
>>> Le mercredi 2 avril 2014 02:34:04 Herv=C3=A9 BOUTEMY a =C3=A9crit :
>>> > Hi Jake,
>>> >
>>> > this page doesn't tell anything about volunteering, and seems not rea=
lly
>>> > updated:
>>> >
>>> > - on "FAQ For PMCs" side,  there is a list of Jenkins admins that see=
ms
>>> > really not accurate
>>> >
>>> http://wiki.apache.org/general/Jenkins#Who_maintains_the_Jenkins_server=
s.3F
>>> >
>>> > - on "FAQ For Administrators" side, the svn link "more info on
>>> > administering" seems not updated
>>> >
>>> > I personnally updated the page with as much recent info as I could, l=
ike
>>> > crius change, but never got feed back nor found who knows more accura=
te
>>> > info (like which slave can be administered by who, since it seems tha=
t
>>> > Windows nodes for example are not like Ubuntu, or Hadoop or Lucene).
>>> >
>>> > So the question remains: how do we sign up?
>>> >
>>> > Regards,
>>> >
>>> > Herv=C3=A9
>>> >
>>> > Le mardi 1 avril 2014 03:03:03 Jake Farrell a =C3=A9crit :
>>> > > Please see http://wiki.apache.org/general/Jenkins for details on th=
e
>>> > > process, thanks again for volunteering, appreciate the help
>>> > >
>>> > > -Jake
>>> > >
>>> > > On Tue, Apr 1, 2014 at 2:24 AM, OmPrakash Muppirala
>>> >
>>> > <bigosmallm@gmail.com>wrote:
>>> > > > 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. Ther=
e
>>> 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 an=
d
>>> 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=C3=A9,
>>> > > > > >
>>> > > > > > 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 t=
o
>>> us
>>> > > >
>>> > > > because
>>> > > >
>>> > > > > > there is no one around to actively maintain and provide suppo=
rt
>>> for
>>> > > > > > it.
>>> > > > > >
>>> > > > > > I know that the admins are volunteers and that they have a re=
al
>>> life
>>> > > > > > as
>>> > > > > > well.  But, I am a volunteer too.  Every week I get only a fe=
w
>>> 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 do=
n'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 th=
e
>>> ASF?
>>> > > >
>>> > > >  What
>>> > > >
>>> > > > > > does it take for the current admins to take notice and realiz=
e
>>> that
>>> > > >
>>> > > > this is
>>> > > >
>>> > > > > > a real problem?
>>> > > > > >
>>> > > > > > Thanks,
>>> > > > > > Om
>>> > > > > >
>>> > > > > >  On Mar 30, 2014 4:47 AM, "Herv=C3=A9 BOUTEMY" <
>>> herve.boutemy@free.fr>
>>> > > >
>>> > > > wrote:
>>> > > > > > > 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 servi=
ce.
>>> > > > > > > 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 o=
n
>>> > > >
>>> > > > problems,
>>> > > >
>>> > > > > > > always
>>> > > > > > > the same 2 or 3 (not all on the wiki page). But they seem t=
o
>>> have
>>> > > >
>>> > > > little
>>> > > >
>>> > > > > > > time
>>> > > > > > > to fix immediate issues. And I don't see any plan for fixin=
g
>>> > > >
>>> > > > recurring
>>> > > >
>>> > > > > > > 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=C3=A9
>>>
>>>
>>



--=20
Sent from my (old) computer