Please provide sufficient steps so that others can duplicate the problem you're reporting.

Based on the stack trace, I'd guess that you inserted USERNAME into one of the fields in the configuration web page.

Screenshots

Steps to reproduce:

1. Setup Global Configuration for git-plugin (Path: C:********\git-cmd.exe
2. For github generated and installed ssh key
3. Allure-report plugin installed as well
4. NodeJS both version 6.9.4 and latest 
5. Jenkins run on localhost
6. URL to remote repository was used in both formats - git@github.com:Username/repo.git and https://github.com/username/repo

The username and useremail parametrs has been added in addition but anyway the same issue still exist.

Building in workspace D:\Jenkins\workspace\example
Cloning the remote Git repository
Cloning repository
> C:\Program Files\Git\git-cmd.exe init D:\Jenkins\workspace-example # timeout=10
Fetching upstream changes from
> C:\Program Files\Git\git-cmd.exe --version # timeout=10
> C:\Program Files\Git\git-cmd.exe fetch --tags
+refs/heads/:refs/remotes/origin/
> C:\Program Files\Git\git-cmd.exe config remote.origin.url

1. timeout=10
   > C:\Program Files\Git\git-cmd.exe config --add remote.origin.fetch +refs/heads/:refs/remotes/origin/ # timeout=10
   > C:\Program Files\Git\git-cmd.exe config remote.origin.url
2. timeout=10
   Fetching upstream changes from
   > C:\Program Files\Git\git-cmd.exe --version # timeout=10
   > C:\Program Files\Git\git-cmd.exe fetch --tags
   +refs/heads/:refs/remotes/origin/
   > C:\Program Files\Git\git-cmd.exe rev-parse "refs/remotes/origin/master^{commit}" # timeout=10
   FATAL: Invalid id: [m]9;8;"USERNAME"@]9;8;"COMPUTERNAME"\ D:\Jenkins\workspace\protractor-allure-reporting-example
   > ]9;12\
   org.eclipse.jgit.errors.InvalidObjectIdException: Invalid id: [m]9;8;"USERNAME"@]9;8;"COMPUTERNAME"\ D:\Jenkins\workspace\protractor-allure-reporting-example
   > ]9;12\
   at org.eclipse.jgit.lib.ObjectId.fromString(ObjectId.java:232)
   at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.revParse(CliGitAPIImpl.java:722)
   at hudson.plugins.git.GitAPI.revParse(GitAPI.java:316)
   at hudson.plugins.git.util.DefaultBuildChooser.getHeadRevision(DefaultBuildChooser.java:130)
   at hudson.plugins.git.util.DefaultBuildChooser.getCandidateRevisions(DefaultBuildChooser.java:112)
   at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:1004)
   at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1111)
   at hudson.scm.SCM.checkout(SCM.java:495)
   at hudson.model.AbstractProject.checkout(AbstractProject.java:1276)
   at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:560)
   at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
   at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:485)
   at hudson.model.Run.execute(Run.java:1735)
   at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
   at hudson.model.ResourceController.execute(ResourceController.java:97)
   at hudson.model.Executor.run(Executor.java:405)
   ERROR: Step ‘Allure Report’ aborted due to exception:
   java.nio.file.NoSuchFileException: D:\Jenkins\workspace\protractor-allure-reporting-example\target\allure-results
   at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)
   at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
   at sun.nio.fs.WindowsLinkSupport.getRealPath(Unknown Source)
   at sun.nio.fs.WindowsPath.toRealPath(Unknown Source)
   at sun.nio.fs.WindowsPath.toRealPath(Unknown Source)
   at ru.yandex.qatools.allure.jenkins.callables.AbstractAddInfo.invoke(AbstractAddInfo.java:23)
   at ru.yandex.qatools.allure.jenkins.callables.AbstractAddInfo.invoke(AbstractAddInfo.java:19)
   at hudson.FilePath.act(FilePath.java:997)
   at hudson.FilePath.act(FilePath.java:975)
   at ru.yandex.qatools.allure.jenkins.AllureReportPublisher.addTestRunInfo(AllureReportPublisher.java:239)
   at ru.yandex.qatools.allure.jenkins.AllureReportPublisher.prepareResults(AllureReportPublisher.java:230)
   at ru.yandex.qatools.allure.jenkins.AllureReportPublisher.perform(AllureReportPublisher.java:93)
   at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:81)
   at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
   at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:735)
   at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:676)
   at hudson.model.Build$BuildExecution.post2(Build.java:186)
   at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:621)
   at hudson.model.Run.execute(Run.java:1760)
   at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
   at hudson.model.ResourceController.execute(ResourceController.java:97)
   at hudson.model.Executor.run(Executor.java:405)
   Finished: FAILURE

I can't duplicate your problem, even with that information.

Some things you might attempt:

1. Describe how you installed command line git. I've never seen a command line git program named "git-cmd.exe". I see one on my computer in the C:\Program Files\Git\git-cmd.exe file, but when I run that program, it does not perform git operations. I believe that program is used to start a command prompt window which includes the git program in its path. If that is your configuration, then I assume you have never successfully cloned anything with git on this Jenkins installation. Change your configuration to either make the git program git, or make it C:\Program Files\Git\cmd\git.exe or make it C:\Program Files\Git\bin\git.exe and see if that helps. If that helps, please describe where you found the recommendation to configure git-cmd.exe as the git program. We need to fix that location
2. Create a new job which is a copy of the problem job. Run it, see if it still fails. If it fails, then the crucial difference between your case and mine is likely in the environment where you're running Jenkins. Explore that environment further, especially around USERNAME and COMPUTERNAME environment variables
3. Wipe the workspace of the problem job. Run it again, see if it still fails. If it does not fail, then the crucial difference between your case and mine is likely in the initial definition of that job. If that is the case, look further at your initial use of parameters to the job
4. Describe the precise versions of the plugins you're using, rather than "latest". The latest version today may not be the latest version next week

Yes, it seems you are right. The issue was in path to git. The correct way is  C:\Program Files\Git\bin\git.exe and only git.exe should be in the path.

gnikita9 that is great news. Was there a location where you found the instructions to use git-cmd.exe (so that we can correct it)?

I think I may want to insert a "safety check" into the git client plugin to give a better warning in case of that mistake. It is already more difficult than I want to make authenticated git repositories work well. I'd love to have one case where an incorrect configuration generates a clear message, instead of a stack trace.

Unfortunately I can't provide the exact place where it was found because there was one of the tickets on stackoverflow if I'm not mistaken

Thanks. I found two stackoverflow articles (here and here) which included the same mistake. Both were describing problems, and neither had a viable answer as far as I could tell.

I've attempted to post a correction, in hopes we'll avoid other users encountering the same problem. We'll see if my limited stackoverflow skills are enough to prevent their moderators from rejecting my answers for failure to follow policy.

Thank you. I'll add a comment with refer link to this post and other posts with similar issue as well. Hope it'll help to avoid this problem.

Configuration error by the user, not ready to support the differences between the supported git commands (git.exe and git.cmd) and the git commands which the plugin does not support (git-cmd.exe and git-bash.exe)