It shouldn't be this difficult. This is wasting our time. A restart fixes most issues most of the time... How hard can it be to give one of us any one of the 7 admin slots that are currently not used on 'windows1'? That way we can manage this for ourselves, saving both us AND the admins time.
I and someone of another project have offered to help out builds@a.oseveral times, but they don't seem interested in improving the current status quo. EdB On Tue, Mar 25, 2014 at 5:03 PM, OmPrakash Muppirala <bigosma...@gmail.com>wrote: > On Mar 25, 2014 7:33 AM, "Alex Harui" <aha...@adobe.com> wrote: > > > > > > > > On 3/25/14 6:33 AM, "OmPrakash Muppirala" <bigosma...@gmail.com> wrote: > > > > > > >But there is no reason why Admins need to not do anything because of > what > > >I > > >was trying to do. I dint think they even noticed that I was trying to > fix > > >the builds. > > > > > >Have they told you otherwise? > > No, but I don't think they can look at the dashboard and figure out they > > need to investigate. Looks like lots of other builds are broken, maybe > by > > bad checkins or other problems that the admins are responsible for. > > > > It seems like the pattern they follow is to wait for a bunch of builds to > go bad and then a restart fixes things. > > > The admins are always overloaded, so if we can find a way to offload > them, > > we'd be better off. I have one more idea if you haven't tried it: What > if > > we said we didn't use an SCM so jenkins didn't try to do the git calls > and > > put the git calls in our jenkins.xml script? > > > > Tried it. Still ran into more weird issues. > > > -Alex > > > -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
