Hi Jonathan, Thanks for the information. I'll follow the new thread.
Best regards, Rachel El martes, 18 de octubre de 2016, 1:17:13 (UTC+2), Jonathan Hodgson escribió: > > Rachel and Martina, > > Thanks for trying to help me on this, I've started a new thread now that > I've realized the issue isn't to do with windows or paths, but rather to do > with slaves and masters. > > On Monday, October 17, 2016 at 11:27:08 PM UTC+1, Jonathan Hodgson wrote: >> >> Well I can confirm that it has nothing to do with it being windows, just >> tried FileNameFinder on my OSX slave and it also looks on the master >> >> On Monday, October 17, 2016 at 9:44:03 PM UTC+1, Jonathan Hodgson wrote: >>> >>> But I don't want to restrict where the job runs, just where the node >>> runs. >>> >>> I have code that needs to run on the master, and code that needs to run >>> on the slaves. >>> >>> The code is running in the correct places, I can for example do a >>> mercurial checkout on the slaves, I can also run batch files on the slaves, >>> and visual studio (or I could, that bit's disabled as I'm working on this, >>> but it worked before). >>> >>> Buildsteps do what they should, on the slave >>> >>> but groovy file commands don't. >>> >>> On Monday, October 17, 2016 at 9:19:45 PM UTC+1, Rachel wrote: >>>> >>>> Hi Jonathan, >>>> >>>> According to master and slave systems you have, I think you might use >>>> the option: >>>> >>>> - "*Restrict where this project can be run*" >>>> >>>> in your job configuration (located in General Configuration), in order *to >>>> force job execution on slave*. >>>> >>>> I hope be useful. >>>> >>>> Best regards, >>>> Rachel >>>> >>>> >>>> El lunes, 17 de octubre de 2016, 22:07:09 (UTC+2), Jonathan Hodgson >>>> escribió: >>>>> >>>>> >>>>> >>>>> On Monday, October 17, 2016 at 8:36:55 PM UTC+1, Martina wrote: >>>>>> >>>>>> So you solved the issue of it running on the wrong system, right? >>>>>> >>>>> >>>>> No, I haven't solved the issue. >>>>> >>>>> I thought perhaps it was running on the wrong system because it didn't >>>>> have an absolute path that it recognized as such, so I was trying to see >>>>> if >>>>> there was a path syntax which made it look locally, so far, no luck >>>>> >>>>> Well, all the "does not exist" messages have a leading /. >>>>>> Not sure where that comes from, but I'm pretty sure that that is what >>>>>> it is complaining about. Also, looking at FileNameFinder, all examples >>>>>> are >>>>>> it finding files, not directories, but examples are clearly using >>>>>> c:/path/path syntax. >>>>>> I'm thinking you may want to try changing up your wildcard to >>>>>> something like '**/*.xml' or '**/*.txt', whatever you actually have on >>>>>> that >>>>>> file system. >>>>>> >>>>>> FilenameFinder works as expected on the master, but not on the slave. >>>>> It doesn't matter what my wildcard is, it always looks on the master. The >>>>> same goes for File... which seems to be the complete opposite of what the >>>>> documentation on File and FilePath says. If I understand that correctly, >>>>> File is always supposed to look on the current machine (i.e. the one that >>>>> node is running on) and so to access stuff on the master you have to use >>>>> FilePath >>>>> >>>>> >>>>> -- You received this message because you are subscribed to the Google Groups "Jenkins Users" 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-users/c6767fd5-5fdd-4941-9255-7c41ef4d1e33%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
