|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Have clearer instructions for reproduction. associated email thread http://goo.gl/HTFGi indicates Reporter found a workaround, but this may still be a bug in FSTrigger - FSTrigger is unable to traverse network shares with a specific Domain\Username & password.
To reproduce:
1. Have the Jenkins ( slave ) running as a windows service as "Local System Account"
2. put in a CIFS path for the FSTrigger directory value
3. FStrigger is unable to access the directory
The workaround is;
1. Have Jenkins running as a windows service with "This account" - an account with access rights to the network share
However, running in this fashion means that "headless" internet explorer testing from Jenkins will not work - it is necessary to have "Allow service to interact with desktop" for IE to run in a pseudo-headless fashion.
FStrigger should have the option to include Domain, Username and encrypted password, in the same manner as the "Publish over CIFS" plugin.