<div dir="ltr">The farm lost connection to Github, so all jobs are failing.<div><br></div><div>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.</div>
<div><br></div><div>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.</div><div><br></div><div>On the front of "hard to understand", the error say this:</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span style="font-family:arial,sans-serif;font-size:13px">Cloning the remote Git repository<br>
</span><span style="font-family:arial,sans-serif;font-size:13px">Cloning repository git://</span><a href="http://github.com/ros-infrastructure/buildfarm.git" target="_blank" style="font-family:arial,sans-serif;font-size:13px">github.com/ros-infrastructure/buildfarm.git<br>
</a><span style="font-family:arial,sans-serif;font-size:13px">Fetching upstream changes from git://</span><a href="http://github.com/ros-infrastructure/buildfarm.git" target="_blank" style="font-family:arial,sans-serif;font-size:13px">github.com/ros-infrastructure/buildfarm.git<br>
</a><span style="font-family:arial,sans-serif;font-size:13px">ERROR: Error cloning remote repo 'origin'</span></blockquote><div><br></div><div>That seems pretty obvious to me that it couldn't fetch upstream changes from github.com...</div>
<div><br></div><div>Again, not sure how this could be more specific, but I am open to suggestions.</div><div> </div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Apr 1, 2014 at 3:49 PM, Austin Hendrix <span dir="ltr"><<a href="mailto:legotown@aol.com" target="_blank">legotown@aol.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">1) you’re a maintainer, so you’re automatically subscribed. There isn’t any more granularity to the email settings than that.<br>
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.<br>
3) yeah… I really can’t help you here<br>
<br>
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.<br>
<br>
-Austin<br>
<div><div class="h5"><br>
On Apr 1, 2014, at 3:45 PM, David Lu!! <<a href="mailto:davidlu@wustl.edu">davidlu@wustl.edu</a>> wrote:<br>
<br>
> So I'd like to start a hopefully constructive discussion of the build<br>
> farm's email practices. I've attached a picture of the onslaught my<br>
> inbox just received. I'm fairly certain none of the builds failing is<br>
> my fault. But it does lead me to some questions.<br>
><br>
> 1) Are there settings for email that I haven't set to reduce the<br>
> number of emails I get? Or am I automatically subscribed because I'm a<br>
> maintainer?<br>
> 2) Is there a way to condense the emails? If I got a single email<br>
> telling me which packages I maintain failed to build, but this seems a<br>
> bit much.<br>
> 3) I've whined about this before, but is there some way we can make<br>
> the error messages more legible? I'm sure for people familiar with the<br>
> build farm, the errors may make sense, but as a maintainer, I have no<br>
> idea what I'm supposed to do. If the answer is nothing, why am I<br>
> getting email?<br>
><br>
> I realize accomplishing some of these tasks will likely involve<br>
> substantial amounts of work, but I feel it merits discussion<br>
> nonetheless.<br>
><br>
> -David<br>
</div></div>> <Screenshot from 2014-04-01 17:30:36.png>_______________________________________________<br>
> ros-release mailing list<br>
> <a href="mailto:ros-release@code.ros.org">ros-release@code.ros.org</a><br>
> <a href="http://lists.ros.org/mailman/listinfo/ros-release" target="_blank">http://lists.ros.org/mailman/listinfo/ros-release</a><br>
<br>
_______________________________________________<br>
ros-release mailing list<br>
<a href="mailto:ros-release@code.ros.org">ros-release@code.ros.org</a><br>
<a href="http://lists.ros.org/mailman/listinfo/ros-release" target="_blank">http://lists.ros.org/mailman/listinfo/ros-release</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>William Woodall<div>ROS Development Team</div><div><a href="mailto:william@osrfoundation.org" target="_blank">william@osrfoundation.org</a></div><div><a href="http://williamjwoodall.com/" target="_blank">http://williamjwoodall.com/</a></div>
</div>