[
https://issues.jenkins-ci.org/browse/JENKINS-12865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159490#comment-159490
]
Brad Huggins commented on JENKINS-12865:
----------------------------------------
I think I might have found the cause of this issue. It appears that after the
Perforce Polling we start seeing this issue. If we don't have Perforce polling
or it hasn't run for the 1st time everything works fine with FSTrigger.
> [ERROR] - SEVERE - Polling error Current Project is null from FSTrigger
> -----------------------------------------------------------------------
>
> Key: JENKINS-12865
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12865
> Project: Jenkins
> Issue Type: Bug
> Components: fstrigger
> Affects Versions: current
> Environment: Linux master (console only no jobs process on it) and a
> Windows slave
> Reporter: Brad Huggins
> Assignee: gbois
> Priority: Blocker
> Attachments: Output-IUS.xml
>
>
> I receive the following error when FSTrigger attempts to poll:
> [FSTrigger] - Monitor files
> Polling for the job Output-ICA
> Polling remotely on *****************
> Polling started on Feb 22, 2012 5:58:09 PM
> [ERROR] - SEVERE - Polling error Current Project is null
> I have attached the configuration file though I scrubbed the server name from
> it. I have tried using \ or / even no path with the same error.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
