There's a few issues in building on windows - the test harness can hide useful failure traces in plugins etc.. and they are slowly starting to be ironed out - we may also have a windows build machine soon so we can do the build/testing on windows...
Jenkins already detects that symbolic links aren't enabled on a windows box when running - so it shouldn't be to hard to actually put in an assumeThat and check the platform. (unless it does this by trying to create a symlink to begin with...) IIRC a group policy is just a fancy way of controlling a load of registry settings - in which case JNA can be used to read the key. /James On Tuesday, 24 March 2015 14:39:11 UTC, Daniel Beck wrote: > > > On 24.03.2015, at 15:32, Olaf Lenz <[email protected] <javascript:>> > wrote: > > > Are there any objections? > > Recommendations like that probably shouldn't be front and center where new > contributors pick them up as the "recommended" settings. We want the tests > to pass, after all. > > If there's a simple way to determine whether the group policy allows > symbolic links and maybe skip the tests if disallowed, that would be a > feasible solution to this issue IMO. > > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/38356f54-6071-4ada-8b90-704a80edf180%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
