[JIRA] [git-plugin] (JENKINS-25289) git notify commit bug when use credentials

[o...@geek.co.il (JIRA)]

Title: Message Title

Oded Arbel commented on JENKINS-25289   Re: git notify commit bug when use credentials This is not a configuration issue, as far as I can tell - and I've read up and down the mailing lists and google groups. This problems is encountered by more than just me and I have not seen any solution except saying "its a configuration issue" until the questioner walks away. My setup is as thus: 1. Linux master 2. passphrase-less key set up using the Jenkins "Credentials" management (with no passphrase, because none is needed). 3. "Force polling using workspace" works around the problem (but that causes other issues with on-demans slaves, as we discussed) 4. Changing to JGit causes a different exception that seems to me like the same problem: ERROR: Failed to record SCM polling for hudson.model.FreeStyleProject@2ae261d[ffmpeg] java.lang.IllegalStateException: Cannot open session, connection is not authenticated. at com.trilead.ssh2.Connection.openSession(Connection.java:1127) at org.jenkinsci.plugins.gitclient.trilead.TrileadSession.exec(TrileadSession.java:32) at org.eclipse.jgit.transport.TransportGitSsh$SshFetchConnection.<init>(TransportGitSsh.java:262) at org.eclipse.jgit.transport.TransportGitSsh.openFetch(TransportGitSsh.java:161) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.getHeadRev(JGitAPIImpl.java:777) at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:583) at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:527) at hudson.scm.SCM.compareRemoteRevisionWith(SCM.java:381) at hudson.scm.SCM.poll(SCM.java:398) at hudson.model.AbstractProject._poll(AbstractProject.java:1459) at hudson.model.AbstractProject.poll(AbstractProject.java:1362) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:510) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:539) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) As far as I can tell, hudson.plugins.git.GitSCM is not setting up the agent with the correct credentials that are configured on the job. I can offer screenshots or any kind of access you need (up to and including ssh into the build server) in order to get this solved. Now, I'm not going to get into a reopen war with Jenkins developers, but closing issues with "its a configuration issue" and with no further details is not productive. If its a configuration issue that you are aware of, then writing a detection for this common problem into the plugin, with a proper error message explaining the issue will be a legitimate way to close this bug. If its not a specific issue that you are aware of, then I'd appreciate it if you can help me figure out what the problem is - and I'll write the detection code to handle this. OK? Add Comment   This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.