[JIRA] (JENKINS-59753) Error cloning remote repo

Issue Type:	Bug
Assignee:	Parichay Barpanda
Components:	gitlab-branch-source-plugin
Created:	2019-10-11 16:10
Environment:	Jenkins ver. 2.190.1 GitLab Branch Source Plugin 1.4.0
Priority:	Major
Reporter:	Guillaume Dupin

Since we use the (great) GitLab Branch Source Plugin, we poncutally have the following error in our jobs :

 
                                                                Current revision of branch master is 885ffa6c168411f6b0f2209d819aa29187e328cf
Obtained Jenkinsfile from 885ffa6c168411f6b0f2209d819aa29187e328cf
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] Start of Pipeline
[Pipeline] node
Still waiting to schedule task
Waiting for next available executor
Running on EC2 (aws-tooling) - Default (i-xxxxx) in /home/jenkins/workspace/zzzzz_master
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Declarative: Checkout SCM)
[Pipeline] checkout
using credential gitlab-jenkins-ssh
Cloning the remote Git repository
Cloning with configured refspecs honoured and without tags
ERROR: Error cloning remote repo 'origin'
hudson.plugins.git.GitException: Command "git fetch --no-tags --progress https://code.tooling.prod.cdsf.io/teh/metadata.deploy.git +refs/heads/master:refs/remotes/origin/master" returned status code 128:
stdout: 
stderr: remote: HTTP Basic: Access denied
fatal: Authentication failed for 'https://code.tooling.prod.cdsf.io/teh/metadata.deploy.git/'

	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2318)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1905)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400(CliGitAPIImpl.java:81)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:488)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:712)
	at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$GitCommandMasterToSlaveCallable.call(RemoteGitImpl.java:161)
	at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$GitCommandMasterToSlaveCallable.call(RemoteGitImpl.java:154)
	at hudson.remoting.UserRequest.perform(UserRequest.java:212)
	at hudson.remoting.UserRequest.perform(UserRequest.java:54)
	at hudson.remoting.Request$2.run(Request.java:369)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
	Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to EC2 (aws-1119-gtp-tooling) - Default (i-09ea841682cf1bd26)
		at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743)
		at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357)
		at hudson.remoting.Channel.call(Channel.java:957)
		at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146)
		at sun.reflect.GeneratedMethodAccessor775.invoke(Unknown Source)
		at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
		at java.lang.reflect.Method.invoke(Method.java:498)
		at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132)
		at com.sun.proxy.$Proxy117.execute(Unknown Source)
		at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1135)
		at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1175)
		at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:124)
		at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:93)
		at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:80)
		at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
		at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
		... 4 more
 
                                                            

To solve this we have to launch a manual scan on the gitlab group.

Are you aware of such intermittent 'configuration' loss please ?

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

gdupin@gmail.com (JIRA)

unread,

Oct 11, 2019, 12:13:03 PM10/11/19

to jenkinsc...@googlegroups.com

Guillaume Dupin updated an issue

Jenkins /

Change By:	Guillaume Dupin

Since we use the (great) GitLab Branch Source Plugin, we poncutally have the following error in our jobs :

{code:java}

Current revision of branch master is 885ffa6c168411f6b0f2209d819aa29187e328cf
Obtained Jenkinsfile from 885ffa6c168411f6b0f2209d819aa29187e328cf
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] Start of Pipeline
[Pipeline] node
Still waiting to schedule task
Waiting for next available executor

Running on EC2 (aws-tooling) - Default (i-xxxxx) in /home/jenkins/workspace/ zzzzz_master zzzzz

[Pipeline] {
[Pipeline] stage
[Pipeline] { (Declarative: Checkout SCM)
[Pipeline] checkout
using credential gitlab-jenkins-ssh
Cloning the remote Git repository
Cloning with configured refspecs honoured and without tags
ERROR: Error cloning remote repo 'origin'

hudson.plugins.git.GitException: Command "git fetch --no-tags --progress https:// code.tooling.prod.cdsf.io URL / teh group / metadata projet . deploy. git +refs/heads/master:refs/remotes/origin/master" returned status code 128:

stdout:
stderr: remote: HTTP Basic: Access denied

fatal: Authentication failed for 'https:// code.tooling.prod.cdsf.io URL / teh group / metadata projet . deploy. git/'

{code}

To solve this we have to launch a manual scan on the gitlab group.

Are you aware of such intermittent 'configuration' loss please ?

lx89757@126.com (JIRA)

unread,

Dec 12, 2019, 1:52:03 AM12/12/19

to jenkinsc...@googlegroups.com

alex li commented on

same issue with https://issues.jenkins-ci.org/browse/JENKINS-60143

tamerlaha@gmail.com (JIRA)

unread,

Jan 14, 2020, 1:38:04 PM1/14/20

to jenkinsc...@googlegroups.com

ipleten commented on

Is there any updates on that?
I found that `doReload()` on job object makes that work again but it also might trigger some unneeded builds.

tamerlaha@gmail.com (JIRA)

unread,

Jan 14, 2020, 1:39:07 PM1/14/20

to jenkinsc...@googlegroups.com

ipleten edited a comment on

Is there any updates on that?
I found that `doReload()` on job object makes that work again but it also might trigger some unneeded builds.

Ugly workaround:
{noformat}
Jenkins.instance.getAllItems(org.jenkinsci.plugins.workflow.multibranch.WorkflowMultiBranchProject.class).each {
it.doReload();
};
{noformat}

per.oestman@gmail.com (JIRA)

unread,

Feb 17, 2020, 8:07:02 AM2/17/20

to jenkinsc...@googlegroups.com

Per Östman commented on

We're seeing a similar issue, only our jobs work when triggered from GitLab push trigger (using SSH checkout), but when triggered from parameterized scheduler trigger, somehow https checkout is used (which cause failure)

The same error occurs occasionally when triggering manually.

Would be great to see some investigation into this!

tamerlaha@gmail.com (JIRA)

unread,

Mar 24, 2020, 3:33:03 PM3/24/20

to jenkinsc...@googlegroups.com

ipleten edited a comment on

Is there any updates on that?
I found that `doReload()` on job object makes that work again but it also might trigger some unneeded builds.
Ugly workaround:
{noformat}
Jenkins.instance.getAllItems(org.jenkinsci.plugins.workflow.multibranch.WorkflowMultiBranchProject.class).each {
it.doReload();
};
{noformat}

Update: Issue happens after each Jenkins restart.

This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)

parichay.barpanda@gmail.com (JIRA)

unread,

Apr 3, 2020, 8:41:07 AM4/3/20

to jenkinsc...@googlegroups.com

Parichay Barpanda started work on

Change By:	Parichay Barpanda
Status:	Open In Progress

parichay.barpanda@gmail.com (JIRA)

unread,

Apr 3, 2020, 8:41:09 AM4/3/20

to jenkinsc...@googlegroups.com

Parichay Barpanda updated

Jenkins /

Change By:	Parichay Barpanda
Status:	In Progress Review

parichay.barpanda@gmail.com (JIRA)

unread,

Apr 3, 2020, 8:44:21 AM4/3/20

to jenkinsc...@googlegroups.com

Parichay Barpanda commented on

Sent fix https://github.com/jenkinsci/gitlab-branch-source-plugin/pull/80

josephp90@gmail.com (JIRA)

unread,

Apr 3, 2020, 2:29:05 PM4/3/20

to jenkinsc...@googlegroups.com

Joseph Petersen updated

Released as 1.4.5

Jenkins /

Change By:	Joseph Petersen
Status:	In Review Resolved
Resolution:	Fixed
Released As:	https://github.com/jenkinsci/gitlab-branch-source-plugin/releases/tag/gitlab-branch-source-1.4.5