You are viewing a plain text version of this content. The canonical link for it is here.
Posted to builds@apache.org by OmPrakash Muppirala <bi...@gmail.com> on 2014/04/01 07:06:12 UTC
Re: volunteering for ASF Jenkins farm service maintenance
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" <he...@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é
>
Re: volunteering for ASF Jenkins farm service maintenance
Posted by Hervé BOUTEMY <he...@free.fr>.
Le jeudi 3 avril 2014 13:48:34 OmPrakash Muppirala a écrit :
> On Thu, Apr 3, 2014 at 1:38 PM, Jake Farrell <jf...@apache.org> wrote:
> > Om, Herve
> > What action are you specifically trying to achieve with the role you are
> > referring to as 'maintainer' ?
>
> Things like setting up builds which require more than just the Jenkins web
> interface, kill stuck jobs, restart machines are required.
+1
investigate at OS level what is happenning when the service isn't behaving
normally
> Add, upgrade/downgrade plugins as required, etc.
personnally, I'm not even hoping adding/upgrading/downgrading plugins until I
better know how maintainers decide, plan, communicate: actually, changing
anything would be adding more noise
But at least being able to see how each build slave is configured more
precisely would permit to document changes.
And my real hope is to create some discussion here between people, problems,
Jenkins admins and Jenkins users, because I suppose not every problem is
caused by Jenkins: some problems are pro
>
> > 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
>
> It does not appear as if there are folks looking at this mailing list to
> evaluate how good a job I am doing here. I would like to know how many
> admins are actually involved with administering Jenkins. With machines
> being offline for days together, build issues not being fixed for weeks
> together, I dont think there are many admins around here. Am I wrong?
+1
http://wiki.apache.org/general/Jenkins#Who_maintains_the_Jenkins_servers.3F
doesn't seem to match the reality
And I suppose Windows slaves are not the same than Unix ones
>
> Who am I supposed to impress with my work so that I get admin access? Is
> it just you?
>
> > http://apache.org/dev/infra-volunteer.html#assist
>
> This link has no mention of Jenkins administration.
>
> > 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
>
> Thanks,
> Om
>
> > On Thu, Apr 3, 2014 at 3:08 PM, OmPrakash Muppirala
<bi...@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
<he...@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
> >>> >
> >>> > <bi...@gmail.com>wrote:
> >>> > > > On Mar 31, 2014 11:15 PM, "Jake Farrell" <jf...@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é
Re: volunteering for ASF Jenkins farm service maintenance
Posted by David Nalley <da...@gnsa.us>.
On Thu, Apr 3, 2014 at 4:48 PM, OmPrakash Muppirala
<bi...@gmail.com> wrote:
> On Thu, Apr 3, 2014 at 1:38 PM, Jake Farrell <jf...@apache.org> wrote:
>
>> Om, Herve
>> What action are you specifically trying to achieve with the role you are
>> referring to as 'maintainer' ?
>>
>
> Things like setting up builds which require more than just the Jenkins web
> interface, kill stuck jobs, restart machines are required. Add,
> upgrade/downgrade plugins as required, etc.
>
>
I realize it seems like a gigantic catch-22. Can't do much without
karma. Need to do things to demonstrate merit to get karma. Far more
difficult than being able to submit patches to a codebase. That said,
it's also pretty far ranging authority that has a widespread effect on
scores of projects, so it's hard to easily hand it out. It also
requires a decent time investment. There's also plenty of low-hanging
fruit that jobadmin is sufficient for.
>>
>> 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
>>
>
> It does not appear as if there are folks looking at this mailing list to
> evaluate how good a job I am doing here. I would like to know how many
> admins are actually involved with administering Jenkins. With machines
> being offline for days together, build issues not being fixed for weeks
> together, I dont think there are many admins around here. Am I wrong?
>
> Who am I supposed to impress with my work so that I get admin access? Is
> it just you?
>
Ultimately I imagine it's the root@ folks who get to make the decision
on granting karma.
>
>>
>> http://apache.org/dev/infra-volunteer.html#assist
>>
>
> This link has no mention of Jenkins administration.
>
>
It also doesn't mention scores of other services Infra maintains, but
the advice remains valid.
--David
Re: volunteering for ASF Jenkins farm service maintenance
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Thu, Apr 3, 2014 at 1:38 PM, Jake Farrell <jf...@apache.org> wrote:
> Om, Herve
> What action are you specifically trying to achieve with the role you are
> referring to as 'maintainer' ?
>
Things like setting up builds which require more than just the Jenkins web
interface, kill stuck jobs, restart machines are required. Add,
upgrade/downgrade plugins as required, etc.
>
> 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
>
It does not appear as if there are folks looking at this mailing list to
evaluate how good a job I am doing here. I would like to know how many
admins are actually involved with administering Jenkins. With machines
being offline for days together, build issues not being fixed for weeks
together, I dont think there are many admins around here. Am I wrong?
Who am I supposed to impress with my work so that I get admin access? Is
it just you?
>
> http://apache.org/dev/infra-volunteer.html#assist
>
This link has no mention of Jenkins administration.
>
> 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
>
>
>
Thanks,
Om
>
>
> On Thu, Apr 3, 2014 at 3:08 PM, OmPrakash Muppirala <bi...@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 <he...@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
>>> >
>>> > <bi...@gmail.com>wrote:
>>> > > > On Mar 31, 2014 11:15 PM, "Jake Farrell" <jf...@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é
>>>
>>>
>>
>
Re: volunteering for ASF Jenkins farm service maintenance
Posted by Robert Munteanu <ro...@lmn.ro>.
On Thu, Apr 3, 2014 at 11:38 PM, Jake Farrell <jf...@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 <bi...@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 <he...@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
>>> >
>>> > <bi...@gmail.com>wrote:
>>> > > > On Mar 31, 2014 11:15 PM, "Jake Farrell" <jf...@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
Re: volunteering for ASF Jenkins farm service maintenance
Posted by Jake Farrell <jf...@apache.org>.
Om, Herve
What action are you specifically trying to achieve with the role you are
referring to as 'maintainer' ?
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 <bi...@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 <he...@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
>> >
>> > <bi...@gmail.com>wrote:
>> > > > On Mar 31, 2014 11:15 PM, "Jake Farrell" <jf...@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é
>>
>>
>
Re: volunteering for ASF Jenkins farm service maintenance
Posted by OmPrakash Muppirala <bi...@gmail.com>.
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 <he...@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
> >
> > <bi...@gmail.com>wrote:
> > > > On Mar 31, 2014 11:15 PM, "Jake Farrell" <jf...@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é
>
>
Re: volunteering for ASF Jenkins farm service maintenance
Posted by Hervé BOUTEMY <he...@free.fr>.
> > 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
>
> <bi...@gmail.com>wrote:
> > > On Mar 31, 2014 11:15 PM, "Jake Farrell" <jf...@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" <he...@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é
Re: volunteering for ASF Jenkins farm service maintenance
Posted by Hervé BOUTEMY <he...@free.fr>.
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
<bi...@gmail.com>wrote:
> > On Mar 31, 2014 11:15 PM, "Jake Farrell" <jf...@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" <he...@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é
Re: volunteering for ASF Jenkins farm service maintenance
Posted by Jake Farrell <jf...@apache.org>.
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 <bi...@gmail.com>wrote:
> On Mar 31, 2014 11:15 PM, "Jake Farrell" <jf...@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" <he...@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é
> > > >
> > >
>
Re: volunteering for ASF Jenkins farm service maintenance
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Mar 31, 2014 11:15 PM, "Jake Farrell" <jf...@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" <he...@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é
> > >
> >
Re: volunteering for ASF Jenkins farm service maintenance
Posted by Jake Farrell <jf...@apache.org>.
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.
Thanks again for your patience in this
-Jake
On Tue, Apr 1, 2014 at 1:06 AM, OmPrakash Muppirala <bi...@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" <he...@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é
> >
>