hudson.plugins.git.GitException

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • How to create Tags in Git with jenkins
    via Stack Overflow by Nikhilesh Dasari
    ,
  • GitHub comment 754#128183183
    via GitHub by heuermh
    ,
  • GitHub comment 53#69847843
    via GitHub by stfeng
    ,
  • The error shows as below after set the *Branch name* from *Additional Behaviours* -> *Check out to specific local branch*. {noformat} > git config core.sparsecheckout > git checkout -f 0bd22591afff0f67e84f9ce97365e1772351b3ce > git branch -a > git rev-parse (detached from 0bd2259)^{commit} FATAL: Could not checkout HEAD with start point 0bd22591afff0f67e84f9ce97365e1772351b3ce hudson.plugins.git.GitException: Could not checkout HEAD with start point 0bd22591afff0f67e84f9ce97365e1772351b3ce at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$8.execute(CliGitAPIImpl.java:1497) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:896) at hudson.model.AbstractProject.checkout(AbstractProject.java:1252) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:513) at hudson.model.Run.execute(Run.java:1710) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: hudson.plugins.git.GitException: Command "git rev-parse (detached from 0bd2259)^{commit}" returned status code 128: stdout: (detached from 0bd2259)^{commit} stderr: fatal: ambiguous argument '(detached from 0bd2259)^{commit}': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]' {noformat} Full Jenkins Console Output has been attached (Jenkins-Git-failed-full-log.txt). After analyzed, the error is because of the *specified colors* set in the ~/.gitconfig. The color settings as blow, details can be found from [my github|https://github.com/Marslo/LinuxStuff/blob/master/Configs/HOME/Git/.gitconfig#L23]: {noformat} [color] ui = true log = always status = always add = always push = always pull = always diff = always branch = always interactive = auto [color "branch"] current = green bold local = yellow remote = red [color "status"] added = yellow changed = red bold untracked = magenta normal dim [color "diff"] meta = blue bold frag = magenta old = red bold new = green bold whitespace = red reverse {noformat} Here the Jenkins job setting: !git-plugin.png! Can git plugin "ignore" the settings automatically (the settings like colors). I've [Created a question in stackoverflow|http://stackoverflow.com/questions/24118259/how-can-jenkins-ignore-the-color-settings-in-gitconfig-by-using-git-plugin]
    via by Marslo Jiao,
    • hudson.plugins.git.GitException: Command "git -c core.askpass=true push github.com/b014081/Project.git Project-193 -f" returned status code 128: stdout: stderr: remote: Permission to b014081/Project.git denied to dcadmin. fatal: unable to access 'github.com/b014081/Project.git/': The requested URL returned error: 403 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1710) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1454) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:63) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$8.execute(CliGitAPIImpl.java:1786)
    No Bugmate found.