hudson.plugins.git.GitException: Unknown git object /master

Jenkins JIRA | Dominik Bartholdi | 3 years ago
  1. 0

    To be able to do a proper release with the maven-release plugin, we need to be running the build on a clean checkout of a branch (not a detached HEAD). I'm trying to do this with the "Additional Behavior" "Check out to specifig local branch" (see screenshot). But when using jgit, I get this exception: {code} Started by user admin [EnvInject] - Loading node environment variables. Building on master in workspace /Users/Shared/Jenkins/Home/jobs/dummy-tester/workspace Fetching changes from the remote Git repository Merging Revision 71099115b31453ae1d17e1808d46a7b6f8782fb4 (origin/master) onto /master FATAL: Unknown git object /master hudson.plugins.git.GitException: Unknown git object /master at org.jenkinsci.plugins.gitclient.JGitAPIImpl.revParse(JGitAPIImpl.java:829) at hudson.plugins.git.extensions.impl.PreBuildMerge.decorateRevisionToBuild(PreBuildMerge.java:60) at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:765) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:832) at hudson.model.AbstractProject.checkout(AbstractProject.java:1387) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:676) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:581) at hudson.model.Run.execute(Run.java:1593) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:491) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:247) {code} When I change the "Branch name" from "master" to "origin/master", it does not fail, but it also does not checkout a branch (I used a shell step with "git branch" to check the branch I'm staying on): {code} Building on master in workspace /Users/Shared/Jenkins/Home/jobs/dummy-tester-jgit/workspace Fetching changes from the remote Git repository Checking out Revision 71099115b31453ae1d17e1808d46a7b6f8782fb4 (origin/master) [workspace] $ /bin/sh -xe /var/folders/c1/m1rcv3kj7g5250lfh3frv_s800009c/T/hudson2838431825011865626.sh + git branch * (no branch) master null origin/master Parsing POMs [workspace] $ java -cp /Users/Shared/Jenkins/Home/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.3.jar:/Users/Shared/Jenkins/Home/tools/hudson.tasks.Maven_MavenInstallation/MVN_303/boot/plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main /Users/Shared/Jenkins/Home/tools/hudson.tasks.Maven_MavenInstallation/MVN_303 /Users/Shared/Jenkins/Home/war/WEB-INF/lib/remoting-2.28.jar /Users/Shared/Jenkins/Home/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-1.3.jar 49195 Picked up _JAVA_OPTIONS: -Dfile.encoding=UTF-8 <===[JENKINS REMOTING CAPACITY]===>channel started {code} Doing the same (Branch name: "master) with cgit, I get this output, also telling that we really stay on a branch: {code} Building on master in workspace /Users/Shared/Jenkins/Home/jobs/dummy-tester-cgit/workspace Fetching changes from the remote Git repository Fetching upstream changes from origin Checking out Revision 71099115b31453ae1d17e1808d46a7b6f8782fb4 (origin/master) First time build. Skipping changelog. [workspace] $ /bin/sh -xe /var/folders/c1/m1rcv3kj7g5250lfh3frv_s800009c/T/hudson1975846668439542655.sh + git branch * master Parsing POMs {code} I also tried the same with the additional behavior "Merge before build", but the result is about the same.

    Jenkins JIRA | 3 years ago | Dominik Bartholdi
    hudson.plugins.git.GitException: Unknown git object /master
  2. 0

    To be able to do a proper release with the maven-release plugin, we need to be running the build on a clean checkout of a branch (not a detached HEAD). I'm trying to do this with the "Additional Behavior" "Check out to specifig local branch" (see screenshot). But when using jgit, I get this exception: {code} Started by user admin [EnvInject] - Loading node environment variables. Building on master in workspace /Users/Shared/Jenkins/Home/jobs/dummy-tester/workspace Fetching changes from the remote Git repository Merging Revision 71099115b31453ae1d17e1808d46a7b6f8782fb4 (origin/master) onto /master FATAL: Unknown git object /master hudson.plugins.git.GitException: Unknown git object /master at org.jenkinsci.plugins.gitclient.JGitAPIImpl.revParse(JGitAPIImpl.java:829) at hudson.plugins.git.extensions.impl.PreBuildMerge.decorateRevisionToBuild(PreBuildMerge.java:60) at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:765) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:832) at hudson.model.AbstractProject.checkout(AbstractProject.java:1387) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:676) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:581) at hudson.model.Run.execute(Run.java:1593) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:491) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:247) {code} When I change the "Branch name" from "master" to "origin/master", it does not fail, but it also does not checkout a branch (I used a shell step with "git branch" to check the branch I'm staying on): {code} Building on master in workspace /Users/Shared/Jenkins/Home/jobs/dummy-tester-jgit/workspace Fetching changes from the remote Git repository Checking out Revision 71099115b31453ae1d17e1808d46a7b6f8782fb4 (origin/master) [workspace] $ /bin/sh -xe /var/folders/c1/m1rcv3kj7g5250lfh3frv_s800009c/T/hudson2838431825011865626.sh + git branch * (no branch) master null origin/master Parsing POMs [workspace] $ java -cp /Users/Shared/Jenkins/Home/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.3.jar:/Users/Shared/Jenkins/Home/tools/hudson.tasks.Maven_MavenInstallation/MVN_303/boot/plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main /Users/Shared/Jenkins/Home/tools/hudson.tasks.Maven_MavenInstallation/MVN_303 /Users/Shared/Jenkins/Home/war/WEB-INF/lib/remoting-2.28.jar /Users/Shared/Jenkins/Home/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-1.3.jar 49195 Picked up _JAVA_OPTIONS: -Dfile.encoding=UTF-8 <===[JENKINS REMOTING CAPACITY]===>channel started {code} Doing the same (Branch name: "master) with cgit, I get this output, also telling that we really stay on a branch: {code} Building on master in workspace /Users/Shared/Jenkins/Home/jobs/dummy-tester-cgit/workspace Fetching changes from the remote Git repository Fetching upstream changes from origin Checking out Revision 71099115b31453ae1d17e1808d46a7b6f8782fb4 (origin/master) First time build. Skipping changelog. [workspace] $ /bin/sh -xe /var/folders/c1/m1rcv3kj7g5250lfh3frv_s800009c/T/hudson1975846668439542655.sh + git branch * master Parsing POMs {code} I also tried the same with the additional behavior "Merge before build", but the result is about the same.

    Jenkins JIRA | 3 years ago | Dominik Bartholdi
    hudson.plugins.git.GitException: Unknown git object /master
  3. 0

    We have a matrix project configured to merge a git feature branch onto the master before starting the build. The exact configuration is attached as screenshot. The documentation for the "Name of repository" oarameter of the "Merge before build" behavior states that: {quote} If left blank, it'll default to the name of the first repository configured above. {quote} However, when leaving this field empty, you receive the following output when triggering the build: {noformat} Started by an SCM change Building remotely on ubuntu_trusty_64bit (trusty gcc ubuntu-next java7 ubuntu linux 64bit) in workspace /home/jenkins/workspace/rsb-cpp-trunk-merge-simulator selected Git installation does not exists. Using Default Wiping out workspace first. Cloning the remote Git repository Cloning repository https://code.cor-lab.org/git/rsb.git.cpp > git init /home/jenkins/workspace/rsb-cpp-trunk-merge-simulator # timeout=10 Fetching upstream changes from https://code.cor-lab.org/git/rsb.git.cpp > git --version # timeout=10 > git fetch --tags --progress https://code.cor-lab.org/git/rsb.git.cpp +refs/heads/*:refs/remotes/origin/* > git config remote.origin.url https://code.cor-lab.org/git/rsb.git.cpp # timeout=10 > git config remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url https://code.cor-lab.org/git/rsb.git.cpp # timeout=10 Fetching upstream changes from https://code.cor-lab.org/git/rsb.git.cpp > git fetch --tags --progress https://code.cor-lab.org/git/rsb.git.cpp +refs/heads/*:refs/remotes/origin/* Seen branch in repository origin/0.10 Seen branch in repository origin/0.3 Seen branch in repository origin/0.4 Seen branch in repository origin/0.5 Seen branch in repository origin/0.6 Seen branch in repository origin/0.7 Seen branch in repository origin/0.9 Seen branch in repository origin/agni Seen branch in repository origin/bug-1285 Seen branch in repository origin/enhancement-1096 Seen branch in repository origin/enhancement-1757 Seen branch in repository origin/enhancement-2034 Seen branch in repository origin/master Seen branch in repository origin/wip-introspection Seen branch in repository origin/wip-rosetta Seen branch in repository origin/wip-static-participants Seen 16 remote branches Multiple candidate revisions Scheduling another build to catch up with rsb-cpp-trunk-merge-simulator Merging Revision 70a3fd1f2425cdc779d83314c6978955979e9237 (origin/enhancement-1757) onto /master using default strategy > git rev-parse /master^{commit} # timeout=10 FATAL: Command "git rev-parse /master^{commit}" returned status code 128: stdout: /master^{commit} stderr: fatal: ambiguous argument '/master^{commit}': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]' hudson.plugins.git.GitException: Command "git rev-parse /master^{commit}" returned status code 128: stdout: /master^{commit} stderr: fatal: ambiguous argument '/master^{commit}': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]' at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1437) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1413) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1409) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1112) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1122) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.revParse(CliGitAPIImpl.java:518) at hudson.plugins.git.GitAPI.revParse(GitAPI.java:257) at sun.reflect.GeneratedMethodAccessor58.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:309) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:290) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:249) 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: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) {noformat}

    Jenkins JIRA | 2 years ago | Johannes Wienke
    hudson.plugins.git.GitException: Command "git rev-parse /master^{commit}" returned status code 128: stdout: /master^{commit} stderr: fatal: ambiguous argument '/master^{commit}': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]'
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    We have a matrix project configured to merge a git feature branch onto the master before starting the build. The exact configuration is attached as screenshot. The documentation for the "Name of repository" oarameter of the "Merge before build" behavior states that: {quote} If left blank, it'll default to the name of the first repository configured above. {quote} However, when leaving this field empty, you receive the following output when triggering the build: {noformat} Started by an SCM change Building remotely on ubuntu_trusty_64bit (trusty gcc ubuntu-next java7 ubuntu linux 64bit) in workspace /home/jenkins/workspace/rsb-cpp-trunk-merge-simulator selected Git installation does not exists. Using Default Wiping out workspace first. Cloning the remote Git repository Cloning repository https://code.cor-lab.org/git/rsb.git.cpp > git init /home/jenkins/workspace/rsb-cpp-trunk-merge-simulator # timeout=10 Fetching upstream changes from https://code.cor-lab.org/git/rsb.git.cpp > git --version # timeout=10 > git fetch --tags --progress https://code.cor-lab.org/git/rsb.git.cpp +refs/heads/*:refs/remotes/origin/* > git config remote.origin.url https://code.cor-lab.org/git/rsb.git.cpp # timeout=10 > git config remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url https://code.cor-lab.org/git/rsb.git.cpp # timeout=10 Fetching upstream changes from https://code.cor-lab.org/git/rsb.git.cpp > git fetch --tags --progress https://code.cor-lab.org/git/rsb.git.cpp +refs/heads/*:refs/remotes/origin/* Seen branch in repository origin/0.10 Seen branch in repository origin/0.3 Seen branch in repository origin/0.4 Seen branch in repository origin/0.5 Seen branch in repository origin/0.6 Seen branch in repository origin/0.7 Seen branch in repository origin/0.9 Seen branch in repository origin/agni Seen branch in repository origin/bug-1285 Seen branch in repository origin/enhancement-1096 Seen branch in repository origin/enhancement-1757 Seen branch in repository origin/enhancement-2034 Seen branch in repository origin/master Seen branch in repository origin/wip-introspection Seen branch in repository origin/wip-rosetta Seen branch in repository origin/wip-static-participants Seen 16 remote branches Multiple candidate revisions Scheduling another build to catch up with rsb-cpp-trunk-merge-simulator Merging Revision 70a3fd1f2425cdc779d83314c6978955979e9237 (origin/enhancement-1757) onto /master using default strategy > git rev-parse /master^{commit} # timeout=10 FATAL: Command "git rev-parse /master^{commit}" returned status code 128: stdout: /master^{commit} stderr: fatal: ambiguous argument '/master^{commit}': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]' hudson.plugins.git.GitException: Command "git rev-parse /master^{commit}" returned status code 128: stdout: /master^{commit} stderr: fatal: ambiguous argument '/master^{commit}': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]' at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1437) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1413) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1409) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1112) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1122) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.revParse(CliGitAPIImpl.java:518) at hudson.plugins.git.GitAPI.revParse(GitAPI.java:257) at sun.reflect.GeneratedMethodAccessor58.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:309) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:290) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:249) 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: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) {noformat}

    Jenkins JIRA | 2 years ago | Johannes Wienke
    hudson.plugins.git.GitException: Command "git rev-parse /master^{commit}" returned status code 128: stdout: /master^{commit} stderr: fatal: ambiguous argument '/master^{commit}': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]'
  6. 0

    We have a matrix project configured to merge a git feature branch onto the master before starting the build. The exact configuration is attached as screenshot. The documentation for the "Name of repository" oarameter of the "Merge before build" behavior states that: {quote} If left blank, it'll default to the name of the first repository configured above. {quote} However, when leaving this field empty, you receive the following output when triggering the build: {noformat} Started by an SCM change Building remotely on ubuntu_trusty_64bit (trusty gcc ubuntu-next java7 ubuntu linux 64bit) in workspace /home/jenkins/workspace/rsb-cpp-trunk-merge-simulator selected Git installation does not exists. Using Default Wiping out workspace first. Cloning the remote Git repository Cloning repository https://code.cor-lab.org/git/rsb.git.cpp > git init /home/jenkins/workspace/rsb-cpp-trunk-merge-simulator # timeout=10 Fetching upstream changes from https://code.cor-lab.org/git/rsb.git.cpp > git --version # timeout=10 > git fetch --tags --progress https://code.cor-lab.org/git/rsb.git.cpp +refs/heads/*:refs/remotes/origin/* > git config remote.origin.url https://code.cor-lab.org/git/rsb.git.cpp # timeout=10 > git config remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url https://code.cor-lab.org/git/rsb.git.cpp # timeout=10 Fetching upstream changes from https://code.cor-lab.org/git/rsb.git.cpp > git fetch --tags --progress https://code.cor-lab.org/git/rsb.git.cpp +refs/heads/*:refs/remotes/origin/* Seen branch in repository origin/0.10 Seen branch in repository origin/0.3 Seen branch in repository origin/0.4 Seen branch in repository origin/0.5 Seen branch in repository origin/0.6 Seen branch in repository origin/0.7 Seen branch in repository origin/0.9 Seen branch in repository origin/agni Seen branch in repository origin/bug-1285 Seen branch in repository origin/enhancement-1096 Seen branch in repository origin/enhancement-1757 Seen branch in repository origin/enhancement-2034 Seen branch in repository origin/master Seen branch in repository origin/wip-introspection Seen branch in repository origin/wip-rosetta Seen branch in repository origin/wip-static-participants Seen 16 remote branches Multiple candidate revisions Scheduling another build to catch up with rsb-cpp-trunk-merge-simulator Merging Revision 70a3fd1f2425cdc779d83314c6978955979e9237 (origin/enhancement-1757) onto /master using default strategy > git rev-parse /master^{commit} # timeout=10 FATAL: Command "git rev-parse /master^{commit}" returned status code 128: stdout: /master^{commit} stderr: fatal: ambiguous argument '/master^{commit}': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]' hudson.plugins.git.GitException: Command "git rev-parse /master^{commit}" returned status code 128: stdout: /master^{commit} stderr: fatal: ambiguous argument '/master^{commit}': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]' at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1437) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1413) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1409) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1112) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1122) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.revParse(CliGitAPIImpl.java:518) at hudson.plugins.git.GitAPI.revParse(GitAPI.java:257) at sun.reflect.GeneratedMethodAccessor58.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:309) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:290) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:249) 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: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) {noformat}

    Jenkins JIRA | 2 years ago | Johannes Wienke
    hudson.plugins.git.GitException: Command "git rev-parse /master^{commit}" returned status code 128: stdout: /master^{commit} stderr: fatal: ambiguous argument '/master^{commit}': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]'

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. hudson.plugins.git.GitException

      Unknown git object /master

      at org.jenkinsci.plugins.gitclient.JGitAPIImpl.revParse()
    2. org.jenkinsci.plugins
      JGitAPIImpl.revParse
      1. org.jenkinsci.plugins.gitclient.JGitAPIImpl.revParse(JGitAPIImpl.java:829)
      1 frame
    3. hudson.plugins.git
      PreBuildMerge.decorateRevisionToBuild
      1. hudson.plugins.git.extensions.impl.PreBuildMerge.decorateRevisionToBuild(PreBuildMerge.java:60)
      1 frame
    4. Hudson GIT plugin
      GitSCM.checkout
      1. hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:765)
      2. hudson.plugins.git.GitSCM.checkout(GitSCM.java:832)
      2 frames
    5. Hudson
      AbstractBuild$AbstractBuildExecution.defaultCheckout
      1. hudson.model.AbstractProject.checkout(AbstractProject.java:1387)
      2. hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:676)
      2 frames
    6. jenkins.scm
      SCMCheckoutStrategy.checkout
      1. jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
      1 frame
    7. Hudson
      Run.execute
      1. hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:581)
      2. hudson.model.Run.execute(Run.java:1593)
      2 frames
    8. Hudson Maven Embedder
      MavenModuleSetBuild.run
      1. hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:491)
      1 frame
    9. Hudson
      Executor.run
      1. hudson.model.ResourceController.execute(ResourceController.java:88)
      2. hudson.model.Executor.run(Executor.java:247)
      2 frames