jenkins-gitlab-merge-request-builder-plugin
jenkins-gitlab-merge-request-builder-plugin copied to clipboard
in queue build will fail if the merge request is merged.
Started by upstream project "CCS-Merge-Auto-CI" build number 186
originally caused by:
Gitlab Merge Request #527 :forkRepo => RC2
Building remotely on 192.168.13.57-Mac (mac) in workspace /Users/jenkins/Public/jenkins/workspace/CCS-Merge-Auto-CI/label/mac
> git rev-parse --is-inside-work-tree
Fetching changes from 2 remote Git repositories
> git config forkRepo
Fetching upstream changes from forkRepo
> git --version
> git fetch --tags --progress forkRepo +refs/heads/*:refs/remotes/forkRepo/*
> git config remote.origin.url mainRepo
Fetching upstream changes from mainRepo
using GIT_SSH to set credentials
> git fetch --tags --progress mainRepo.git +refs/heads/*:refs/remotes/origin/*
Checking out Revision 6172429b584b6c9604accce41aad674e91c9bbf4 ()
> git config core.sparsecheckout
> git checkout -f 6172429b584b6c9604accce41aad674e91c9bbf4
FATAL: Could not checkout null with start point 6172429b584b6c9604accce41aad674e91c9bbf4
hudson.plugins.git.GitException: Could not checkout null with start point 6172429b584b6c9604accce41aad674e91c9bbf4
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$8.execute(CliGitAPIImpl.java:1578)
at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153)
at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:328)
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:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: hudson.plugins.git.GitException: Command "git checkout -f 6172429b584b6c9604accce41aad674e91c9bbf4" returned status code 128:
stdout:
stderr: fatal: reference is not a tree: 6172429b584b6c9604accce41aad674e91c9bbf4
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1406)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1382)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1378)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1092)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1102)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$8.execute(CliGitAPIImpl.java:1573)
... 10 more
I remove our git urls from this log
the `hudson.plugins.git.GitException: Command "git checkout -f 6172429b584b6c9604accce41aad674e91c9bbf4" returned status code 128: stdout: ' error looks happen often, but unknown why it doesn't get enough attention. @timols do do mind to take a look at this or give any instructions to search for others? looks the bad commit is cached somewhere, if I can workaround the issue by remove the cache, it will be good enough for me.