Beware, we had a spider hit our jenkins/hudson and test rack sytem once, and found it managed to hit things all over our installation. we had a morning of growing chaos, with a 'pull the damn network cable out' moment, before figure out what had happened. We managed to find the IP of the spider, and ask them to exclude the entire IP range of our racks - which they complied with. Among other things, it was hitting web services we have to lock bits of hardware for a test to use - so stuff was randomly locking/unlocking.
Try to find the IP address of the thing doing it - perhaps from the wrapper logs. On 27 February 2012 20:13, grayaii <george.g...@rsa.com> wrote: > What a coincidence, we just got hit by this same exact problem today. > > So if I understand correctly, polling will disable the job if the SVN url > is > incorrect? > > This is really bad news for us because we use the "Prepare an environment > of > the job" plugin, which makes our SVN path look this: > > https://my.svn.com/svn/src/branches/*$BRANCH_NAME* > > It works fine if I run the job, but polling will not resolve the url... and > then disable the job. > > Argh. I didn't notice this until polling occurs, and now I have a whole > bunch of disabled jobs. > > > > -- > View this message in context: > http://jenkins.361315.n4.nabble.com/anonymous-disables-jobs-tp4417803p4425897.html > Sent from the Jenkins users mailing list archive at Nabble.com. > -- Danny Staple Director, ODM Solutions Ltd w: http://www.odmsolutions.co.uk Blog: http://orionrobots.co.uk/blog1-Danny-Staple
