Re: Jenkins build is back to normal : java-opensaml-multi-test » JDK-1.7.0,WindowsServer2012 #2

[Brent Putman]

On 1/15/16 3:38 PM, Tom Zeller wrote:
>> Yay.
> +1.
>
> P.S. Nothing to see here, but … I’m going to delete java-opensaml-multi-test and re-run java-opensaml-multi-jdk, which needs to be renamed to java-opensaml-multi. You triggered a tmp job I didn’t mean to leave laying around, no big deal.

Ah, ok.  I was wondering what that was.  I just ran the one that was
reporting failure on the commits list.

Only question/concern I had here was whether just doing a simple 'svn
update' would change the file line endings if the svn:eol-style prop
had changed.  Or whether you needed to delete the files and then 'svn
update' to recreate them.  I'm pretty sure if Jenkins checks out an
entirely fresh working copy, that will be in the right state.