Error validating crumb
One solution to avoid entering your password (the one you defined in the ssh key in the process above) is to use
Visit the link below for more details: Clusters/pka-putty.html* future *integration with ssh-credentials-plugin could help If you did everything, you should now have a ~/folder (c:\Users\Bob\for instance) and this folder contains your keys.
Please refer to the online help of each of the additional options for further information. ", which would populate the remote server info in your ~/.ssh/known_hosts.
Started by user anonymous Checkout:workspace / C:\Documents and Settings\Administrator\.hudson\jobs\watir\workspace - hudson.remoting. Even with proper SSH keys set up for the Jenkins user, if you don't have a properly configured ~/.ssh/known_hosts, the build will still hang.
Local [email protected] Last Build : #4 Checkout:workspace / C:\Documents and Settings\Administrator\.hudson\jobs\watir\workspace - hudson.remoting. A quick way to generate this known_hosts file is to copy your Jenkins build SSH keys into C:\Program Files (x86)\Git\(so that can find them), and run This will populate C:\Program Files (x86)\Git\.ssh\known_hosts and then you can just copy C:\Program Files (x86)\Git\to C:\Windows\Sys WOW64\config\systemprofile\(the “Local System account” home).
Local [email protected] Cloning the remote Git repository Cloning repository origin $ git clone -o origin git://github.com/bret/"C:\Documents and Settings\Administrator\.hudson\jobs\watir\workspace" Trying next repository ERROR: Could not clone from a repository FATAL: Could not clone hudson. For a more detailed tutorial, see of all, if your system/user never connected to the git server, you will have to add the server to your list of trusted servers. SO if you run jenkins as user 'John', make sure you login as 'John' before running the previous command.
RSA key fingerprint is 41:d2:d:7d:bd:0d:5e:3f:19:db:5d:34:4d:9d. Are you sure you want to continue connecting (yes/no)? The registry entries added for a specific user can be found here: Once this is done, make sure you restart your consoles and the jenkins service. The public key will have to be added/installed on the server.The git client plugin provides multiple git implementations.The default git implementation relies on command line git. Administrators can enable a pure java implementation of the git protocol from the "Git" button in "Manage Jenkins" "Global Tool Configuration". Once JGit (or JGit apache) has been added, jobs will include a picklist "Git executable" in the git configuration section of the job.The git-client plugin 1.0.4 used JGit by default, while still including the command line Git implementation as an alternate implementation.