www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Munteanu <rob...@lmn.ro>
Subject Re: volunteering for ASF Jenkins farm service maintenance
Date Sat, 05 Apr 2014 20:04:50 GMT
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/puppet,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 any
> 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, either
> 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 out
>> 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é BOUTEMY <herve.boutemy@free.fr>wrote:
>>
>>> > >  thanks again for volunteering, appreciate the help
>>> was this an april's fool?
>>>
>>> Regards,
>>>
>>> Hervé
>>>
>>> Le mercredi 2 avril 2014 02:34:04 Hervé BOUTEMY a écrit :
>>> > Hi Jake,
>>> >
>>> > this page doesn't tell anything about volunteering, and seems not really
>>> > updated:
>>> >
>>> > - on "FAQ For PMCs" side,  there is a list of Jenkins admins that seems
>>> > really not accurate
>>> >
>>> http://wiki.apache.org/general/Jenkins#Who_maintains_the_Jenkins_servers.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, like
>>> > crius change, but never got feed back nor found who knows more accurate
>>> > info (like which slave can be administered by who, since it seems that
>>> > Windows nodes for example are not like Ubuntu, or Hadoop or Lucene).
>>> >
>>> > So the question remains: how do we sign up?
>>> >
>>> > Regards,
>>> >
>>> > Hervé
>>> >
>>> > Le mardi 1 avril 2014 03:03:03 Jake Farrell a écrit :
>>> > > Please see http://wiki.apache.org/general/Jenkins for details on the
>>> > > 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.
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é,
>>> > > > > >
>>> > > > > > 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é 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 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
>>> > > >
>>> > > > 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é
>>>
>>>
>>



-- 
Sent from my (old) computer

Mime
View raw message