[JIRA] [git] (JENKINS-24809) Github-Jenkins Trigger issue with slave

[mark.earl.wa...@gmail.com (JIRA)]

Mark Waite commented on JENKINS-24809 Github-Jenkins Trigger issue with slave There are certainly many installations worldwide which use a wide mix of Windows and Linux computers, and which successfully poll whether or not "Force polling workspace" is set. You may have a configuration error in your Jenkins setup. Some things you might try as a way to test that theory: Configure a freestyle job with Git as scm from a repository accessible from all your machines (maybe https://github.com/jenkinsci/git-client-plugin.git) Configure that job to "Force polling using workspace" and configure it to poll once a minute Configure the job to limit which node can run the job, limit it to the master node Read the polling log to confirm it was successful Configure the job to limit which node can run the job, limit it to another node Wait for it to poll from that node Read the polling log to see if the polling commands are successful from that node Iterate through each of your nodes, confirming that each is able to poll with git If one of the nodes is discovered that it cannot poll with git, then you can review the configuration of that node, looking to see if it has incorrectly declared the location of the git program, or if it is incorrectly using the git location of the master node.

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/d/optout.