[FSTrigger] Scanning a network folder such as \\some_network_folder\to_scan doesn't work

[Benjamin Calvot]

Hi,

 

I am trying to use the FSTrigger plugin but it doesn’t seem to work with network folders (whether scanning files or folder).

 

FSTrigger Files Log gives me:

 

        Polling on the master

        The folder path '\\some_network_folder\to_scan' doesn't exist.

        The computed file doesn't exist.

 

And FSTrigger Folder Log gives me:

 

        Polling on the master

        Trying to monitor the folder '\\some_network_folder\to_scan'

        The directory '\\some_network_folder\to_scan' doesn't exist.

In order to narrow down the problem I tried with a local folder on the master like C:\TEST and it works fine. Then I tried again over the network but using a network drive I created, like Z:\ mapped to \\some_network_folder\to_scan, but it didn’t work.

 

Am I missing something?

Thanks in advance,

 

Benjamin

 

[Grégory Boissinot]

Could you try to double slash?
For example, try to give \\\\some_network_folder\\to_scan

[Benjamin Calvot]

No, that’s exactly the same thing:

 

Polling on the master

The folder path '\\\\some_network_folder\\to_scan\' doesn't exist.

The computed file doesn't exist

 

Polling on the master

Trying to monitor the folder '\\\\some_network_folder\\to_scan'

The directory '\\some_network_folder\to_scan' doesn't exist.

 

Is there a simple way for me to add logs around, say, FolderContentTrigger.getFileInfo()? I’m not a Java developer but this code is simple enough for me.

 

Thanks in advance!

Benjamin

 

 

De : jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] De la part de Grégory Boissinot
Envoyé : lundi 9 janvier 2012 22:57
À : jenkins...@googlegroups.com
Objet : Re: [FSTrigger] Scanning a network folder such as \\some_network_folder\to_scan doesn't work

[Grégory Boissinot]

Thanks for your test.
Could you raise a bug report in the Jenkins issue tracker?
I have to test it on Windows.
I'll fix it as soon as possible.
Thanks in advance.

[Sami Tikka]

A common problem with windows users is that Jenkins is not able to access network locations. This is usually caused by the Jenkins user not having permission to do so. 

-- Sami

[Benjamin Calvot]

Well, it might be the problem indeed, since I am running Jenkins as a service using “Local System Account” login. So I tried to use the same login that the slaves are using, but Jenkins never came back up again (the service was running but Jenkins was saying “please wait…”).

 

Grégory, before investigating the bug further you might want to wait until I manage to make Jenkins work with the right account.

 

Benjamin

 

De : jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] De la part de Sami Tikka
Envoyé : mardi 10 janvier 2012 18:39

À : jenkins...@googlegroups.com
Objet : Re: [FSTrigger] Scanning a network folder such as \\some_network_folder\to_scan doesn't work

 

A common problem with windows users is that Jenkins is not able to access network locations. This is usually caused by the Jenkins user not having permission to do so. 

-- Sami

[Benjamin Calvot]

So, I’ve never managed to make the service work with the right user. The thing is I’m not the one who installed Jenkins and I’m not sure how it is actually started, but I suspect some sort of service wrapper. And it doesn’t like to be given another user as the “local system account”.

 

Anyway, I’ve run a test on another machine on which I installed Jenkins inside Tomcat, and with the user account I wanted, and *the FSTrigger plugin now works perfectly* :-)

 

I’m sorry for the red herring, you can probably close the JIRA, Gregory.

 

Thanks for your help,

Benjamin

 

De : jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] De la part de Benjamin Calvot
Envoyé : mercredi 11 janvier 2012 18:55
À : jenkins...@googlegroups.com
Objet : RE: [FSTrigger] Scanning a network folder such as \\some_network_folder\to_scan doesn't work