The farm lost connection to Github, so all jobs are failing.
I don't see a good way for us to automatically tell the difference between
you put something in your package which causes it to fail (bad url or bug)
and we can't reach github.
I agree that it sucks to get lots of emails about this, but I can't think
of any way to improve it. I am open to suggestions on how to do that.
On the front of "hard to understand", the error say this:
Cloning the remote Git repository
> Cloning repository git://github.com/ros-infrastructure/buildfarm.git
> Fetching upstream changes from git://
> github.com/ros-infrastructure/buildfarm.git
> ERROR: Error cloning remote repo 'origin'
That seems pretty obvious to me that it couldn't fetch upstream changes
from github.com...
Again, not sure how this could be more specific, but I am open to
suggestions.
On Tue, Apr 1, 2014 at 3:49 PM, Austin Hendrix <
legotown@aol.com> wrote:
> 1) you're a maintainer, so you're automatically subscribed. There isn't
> any more granularity to the email settings than that.
> 2) There aren't any settings for this that I'm aware of, but there may be
> an alternate jenkins notification plugin that can do this. It's probably
> worth looking into.
> 3) yeah... I really can't help you here
>
> Not a real solution, but I filter the emails that I get from jenkins into
> a separate tag/folder in my email client, so that I can put off looking at
> them until later.
>
> -Austin
>
> On Apr 1, 2014, at 3:45 PM, David Lu!! <davidlu@wustl.edu> wrote:
>
> > So I'd like to start a hopefully constructive discussion of the build
> > farm's email practices. I've attached a picture of the onslaught my
> > inbox just received. I'm fairly certain none of the builds failing is
> > my fault. But it does lead me to some questions.
> >
> > 1) Are there settings for email that I haven't set to reduce the
> > number of emails I get? Or am I automatically subscribed because I'm a
> > maintainer?
> > 2) Is there a way to condense the emails? If I got a single email
> > telling me which packages I maintain failed to build, but this seems a
> > bit much.
> > 3) I've whined about this before, but is there some way we can make
> > the error messages more legible? I'm sure for people familiar with the
> > build farm, the errors may make sense, but as a maintainer, I have no
> > idea what I'm supposed to do. If the answer is nothing, why am I
> > getting email?
> >
> > I realize accomplishing some of these tasks will likely involve
> > substantial amounts of work, but I feel it merits discussion
> > nonetheless.
> >
> > -David
> > <Screenshot from 2014-04-01
> 17:30:36.png>_______________________________________________
> > ros-release mailing list
> > ros-release@code.ros.org
> > http://lists.ros.org/mailman/listinfo/ros-release
>
> _______________________________________________
> ros-release mailing list
> ros-release@code.ros.org
> http://lists.ros.org/mailman/listinfo/ros-release
>
--
William Woodall
ROS Development Team
william@osrfoundation.org
http://williamjwoodall.com/
_______________________________________________
ros-release mailing list
ros-release@code.ros.org
http://lists.ros.org/mailman/listinfo/ros-release
%0A>%20and%20we%20can't%20reach%20github.%0A>%20%0A>%20I%20agree%20that%20it%20sucks%20to%20get%20lots%20of%20emails%20about%20this,%20but%20I%20can't%20think%0A>%20of%20any%20way%20to%20improve%20it.%20I%20am%20open%20to%20suggestions%20on%20how%20to%20do%20that.%0A>%20%0A>%20On%20the%20front%20of%20%22hard%20to%20understand%22,%20the%20error%20say%20this:%0A>%20%0A>%20Cloning%20the%20remote%20Git%20repository%0A>%20>%20Cloning%20repository%20git://github.com/ros-infrastructure/buildfarm.git%0A>%20>%20Fetching%20upstream%20changes%20from%20git://%0A>%20>%20github.com/ros-infrastructure/buildfarm.git%0A>%20>%20ERROR:%20Error%20cloning%20remote%20repo%20'origin'%0A>%20%0A>%20%0A>%20That%20seems%20pretty%20obvious%20to%20me%20that%20it%20couldn't%20fetch%20upstream%20changes%0A>%20from%20github.com...%0A>%20%0A>%20Again,%20not%20sure%20how%20this%20could%20be%20more%20specific,%20but%20I%20am%20open%20to%0A>%20suggestions.%0A>%20%0A>%20%0A>%20%0A>%20On%20Tue,%20Apr%201,%202014%20at%203:49%20PM,%20Austin%20Hendrix%20<legotown@aol.com>%20wrote:%0A>%20%0A>%20>%201)%20you're%20a%20maintainer,%20so%20you're%20automatically%20subscribed.%20There%20isn't%0A>%20>%20any%20more%20granularity%20to%20the%20email%20settings%20than%20that.%0A>%20>%202)%20There%20aren't%20any%20settings%20for%20this%20that%20I'm%20aware%20of,%20but%20there%20may%20be%0A>%20>%20an%20alternate%20jenkins%20notification%20plugin%20that%20can%20do%20this.%20It's%20probably%0A>%20>%20worth%20looking%20into.%0A>%20>%203)%20yeah...%20I%20really%20can't%20help%20you%20here%0A>%20>%0A>%20>%20Not%20a%20real%20solution,%20but%20I%20filter%20the%20emails%20that%20I%20get%20from%20jenkins%20into%0A>%20>%20a%20separate%20tag/folder%20in%20my%20email%20client,%20so%20that%20I%20can%20put%20off%20looking%20at%0A>%20>%20them%20until%20later.%0A>%20>%0A>%20>%20-Austin%0A>%20>%0A>%20>%20On%20Apr%201,%202014,%20at%203:45%20PM,%20David%20Lu!!%20<davidlu@wustl.edu>%20wrote:%0A>%20>%0A>%20>%20>%20So%20I'd%20like%20to%20start%20a%20hopefully%20constructive%20discussion%20of%20the%20build%0A>%20>%20>%20farm's%20email%20practices.%20I've%20attached%20a%20picture%20of%20the%20onslaught%20my%0A>%20>%20>%20inbox%20just%20received.%20I'm%20fairly%20certain%20none%20of%20the%20builds%20failing%20is%0A>%20>%20>%20my%20fault.%20But%20it%20does%20lead%20me%20to%20some%20questions.%0A>%20>%20>%0A>%20>%20>%201)%20Are%20there%20settings%20for%20email%20that%20I%20haven't%20set%20to%20reduce%20the%0A>%20>%20>%20number%20of%20emails%20I%20get?%20Or%20am%20I%20automatically%20subscribed%20because%20I'm%20a%0A>%20>%20>%20maintainer?%0A>%20>%20>%202)%20Is%20there%20a%20way%20to%20condense%20the%20emails?%20If%20I%20got%20a%20single%20email%0A>%20>%20>%20telling%20me%20which%20packages%20I%20maintain%20failed%20to%20build,%20but%20this%20seems%20a%0A>%20>%20>%20bit%20much.%0A>%20>%20>%203)%20I've%20whined%20about%20this%20before,%20but%20is%20there%20some%20way%20we%20can%20make%0A>%20>%20>%20the%20error%20messages%20more%20legible?%20I'm%20sure%20for%20people%20familiar%20with%20the%0A>%20>%20>%20build%20farm,%20the%20errors%20may%20make%20sense,%20but%20as%20a%20maintainer,%20I%20have%20no%0A>%20>%20>%20idea%20what%20I'm%20supposed%20to%20do.%20If%20the%20answer%20is%20nothing,%20why%20am%20I%0A>%20>%20>%20getting%20email?%0A>%20>%20>%0A>%20>%20>%20I%20realize%20accomplishing%20some%20of%20these%20tasks%20will%20likely%20involve%0A>%20>%20>%20substantial%20amounts%20of%20work,%20but%20I%20feel%20it%20merits%20discussion%0A>%20>%20>%20nonetheless.%0A>%20>%20>%0A>%20>%20>%20-David%0A>%20>%20>%20<Screenshot%20from%202014-04-01%0A>%20>%2017:30:36.png>_______________________________________________%0A>%20>%20>%20ros-release%20mailing%20list%0A>%20>%20>%20ros-release@code.ros.org%0A>%20>%20>%20http://lists.ros.org/mailman/listinfo/ros-release%0A>%20>%0A>%20>%20_______________________________________________%0A>%20>%20ros-release%20mailing%20list%0A>%20>%20ros-release@code.ros.org%0A>%20>%20http://lists.ros.org/mailman/listinfo/ros-release%0A>%20>%0A>%20%0A>%20%0A>%20%0A>%20--%20%0A>%20William%20Woodall%0A>%20ROS%20Development%20Team%0A>%20william@osrfoundation.org%0A>%20http://williamjwoodall.com/%0A>%20_______________________________________________%0A>%20ros-release%20mailing%20list%0A>%20ros-release@code.ros.org%0A>%20http://lists.ros.org/mailman/listinfo/ros-release%0A>%20 "Besvar denne besked")
(text/plain)