ssh: command not found
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

indicates that the git program did not have its PATH correctly configured to find the ssh executable which it uses for authenticated access to the remote server. If that job was configured with "Force polling using workspace", then that means the machine on which the workspace exists does not have the ssh command in its PATH.

You can check that by creating a job which runs on that same machine and reports the value of the PATH environment variable.

You can also review the environment variables of the slave through the "nodes" panel in Jenkins (http://localhost:8080/computer/). Each node has a "System Information" link which shows a page of the various settings used as defaults on that node. Those are defaults, and can be overridden by jobs, but it may be worth checking that the defaults are what you expect for that computer and operating system.

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 [email protected].
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-plugin] (JENKINS-25552) Git Polling with keys fails for Windows master and OSX slave

Reply via email to