[JIRA] [git-client-plugin] (JENKINS-32712) Job with Git polling "succeeds" with "no changes" although the Git polling failed

2 views
Skip to first unread message

michael.friess@mgm-tp.com (JIRA)

unread,
Feb 1, 2016, 12:48:04 PM2/1/16
to jenkinsc...@googlegroups.com
Michael F. created an issue
 
Jenkins / Bug JENKINS-32712
Job with Git polling "succeeds" with "no changes" although the Git polling failed
Issue Type: Bug Bug
Assignee: Nicolas De Loof
Components: git-client-plugin, git-plugin
Created: 01/Feb/16 5:47 PM
Environment: Jenkins ver. 1.625.2
Git Plugin 2.4.1
Gerrit repository on the origin side with SSH authentification
Priority: Minor Minor
Reporter: Michael F.

Reproduction:

  • Take a working job with Git SCM Polling enabled (with the fast / "ls-remote" method)
  • Provoke an error in the origin response (e.g. see Log below)
  • Git Polling ends with "No changes"
  • The Job stays at "blue" (successful) although the Polling clearly had errors --> the not working job might stay undiscovered quite long

Git Polling Log:

Started on Jan 31, 2016 10:00:00 PM
Using strategy: Default
[poll] Last Built Revision: Revision 1231223345345345345345345345345345345543 (refs/remotes/origin/master)
using GIT_SSH to set credentials SSH Key for someUser
 > git --version # timeout=10
 > git -c core.askpass=true ls-remote -h ssh://someUser@localhost/example-projects/example1 # timeout=10
FATAL: hudson.plugins.git.GitException: Command "git -c core.askpass=true ls-remote -h ssh://someUser@localhost/example-projects/example1" returned status code 128:
stdout: 
stderr: fatal: Project not found: example-projects/example1
fatal: Could not read from remote repository.

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

hudson.util.IOException2: hudson.plugins.git.GitException: Command "git -c core.askpass=true ls-remote -h ssh://someUser@localhost/example-projects/example1" returned status code 128:
stdout: 
stderr: fatal: Project not found: example-projects/example1
fatal: Could not read from remote repository.

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

	at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:529)
	at hudson.scm.SCM.compareRemoteRevisionWith(SCM.java:381)
	at hudson.scm.SCM.poll(SCM.java:398)
	at hudson.model.AbstractProject._poll(AbstractProject.java:1452)
	at hudson.model.AbstractProject.poll(AbstractProject.java:1355)
	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)
Caused by: hudson.plugins.git.GitException: Command "git -c core.askpass=true ls-remote -h ssh://someUser@localhost/example-projects/example1" returned status code 128:
stdout: 
stderr: fatal: Project not found: example-projects/example1
fatal: Could not read from remote repository.

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

	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1693)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1441)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1335)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1326)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getHeadRev(CliGitAPIImpl.java:2435)
	at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:583)
	at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:527)
	... 12 more
Done. Took 0.42 sec
No changes
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
Atlassian logo

mark.earl.waite@gmail.com (JIRA)

unread,
Feb 2, 2016, 3:18:01 PM2/2/16
to jenkinsc...@googlegroups.com
Mark Waite assigned an issue to Unassigned
Change By: Mark Waite
Assignee: Nicolas De Loof

mark.earl.waite@gmail.com (JIRA)

unread,
Feb 3, 2016, 6:06:01 PM2/3/16
to jenkinsc...@googlegroups.com
Mark Waite commented on Bug JENKINS-32712
 
Re: Job with Git polling "succeeds" with "no changes" although the Git polling failed

I'm not sure there is currently any location to show that git polling failed. The results of the individual jobs are not dependent on a polling failure, so showing the most recent job as a failure due to a polling failure seems like the wrong choice.

Would it be helpful if the git polling log line in the job page were changed somehow to show that polling failed? For example, if the red text "(failed)" were appended to the line which currently says "Git polling log"?

Alternately, would it help if the polling log icon were changed from the current clipboard icon to a clipboard behind a "red slashed circle"?

I'm not ready to implement either of those ideas yet, but I can see how they would help me when I'm testing the plugin, since I could more easily see which jobs had a polling failure, instead of requiring that I visit each job and open each git polling log.

thorsten.kahler@dkd.de (JIRA)

unread,
Feb 4, 2016, 12:16:02 PM2/4/16
to jenkinsc...@googlegroups.com

Waiting for a code change to reach integration while it's stuck on the Git server ain't nice. So IMO there should at least be the option to mark a build as failed or unstable, if the Git polling failed. Suppressing such failures might be configurable via "Additional Behaviours".

mark.earl.waite@gmail.com (JIRA)

unread,
Feb 9, 2016, 5:29:05 PM2/9/16
to jenkinsc...@googlegroups.com
Mark Waite updated an issue
 
Jenkins / New Feature JENKINS-32712
Change By: Mark Waite
Issue Type: Bug New Feature

michael_giroux@choicehotels.com (JIRA)

unread,
Feb 29, 2016, 12:54:03 AM2/29/16
to jenkinsc...@googlegroups.com

> I'm not sure there is currently any location to show that git polling failed.

Perhaps this type of failure could result in a job being triggered. The job would fail (hopefully) during the git checkout leaving the git responses in the job's console output.

bobbytait@gmail.com (JIRA)

unread,
Apr 6, 2016, 2:34:01 PM4/6/16
to jenkinsc...@googlegroups.com

We've just discovered this issue too, and we typically use Jenkins as a fire-and-forget build tool until we're notified that a problem has occurred. Someone noticed we hadn't received any scheduled builds in a couple of days, despite new code pushes.

For us, having some external notification telling us there was a problem with Jenkins that we need to check out immediately would be ideal. Something like an email or build failure (which would also send an email) or something else I'm not thinking of at the moment.
Reply all
Reply to author
Forward
0 new messages