Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Labels:
      None
    • Environment:
      Jenkins ver. 2.190.1
      GitLab Branch Source Plugin 1.4.0
    • Similar Issues:

      Description

      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
      [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://URL/group/projet.git +refs/heads/master:refs/remotes/origin/master" returned status code 128:
      stdout: 
      stderr: remote: HTTP Basic: Access denied
      fatal: Authentication failed for 'https://URL/group/projet.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 ?

        Attachments

          Issue Links

            Activity

            Hide
            sora alex li added a comment -
            Show
            sora alex li added a comment - same issue with  https://issues.jenkins-ci.org/browse/JENKINS-60143
            Hide
            tamerlaha ipleten added a comment - - edited

            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:

            Jenkins.instance.getAllItems(org.jenkinsci.plugins.workflow.multibranch.WorkflowMultiBranchProject.class).each {
              	it.doReload();
              };
            
            Show
            tamerlaha ipleten added a comment - - edited 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: Jenkins.instance.getAllItems(org.jenkinsci.plugins.workflow.multibranch.WorkflowMultiBranchProject.class).each { it.doReload(); };
            Hide
            postman Per Östman added a comment -

            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!

            Show
            postman Per Östman added a comment - 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!

              People

              • Assignee:
                baymac Parichay Barpanda
                Reporter:
                yogeek Guillaume Dupin
              • Votes:
                2 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated: