Weird, especially since it says there were no changes in the builds, and
since the build before and after are all correct...
Maybe some connection issues to another repo during the build? But then it
would have been notified in the console output...
Let us know if you find out!
On Sun, Jun 30,
Must of been a mistake
On Sun, Jun 30, 2013 at 10:12 AM, Scott Kitterman wrote:
> This is the first Jenkins failure mail I've gotten. I can't make sense of
> it.
> Was there even a test run? Why was the mail sent?
>
> Scott K
>
> -- Forwarded Message --
>
> Subject: Jenkins F
