-
Bug
-
Resolution: Unresolved
-
Major
-
None
Default refspec according to the documentation is
+refs/heads/*:refs/remotes/REPOSITORYNAME/*
When I click on "Trigger build" in Stash's pull request overview, my job fails, because it cannot find commit in the specified refspecs (because commit is in pull requests, not in heads).
> C:\Program Files (x86)\Git\bin\git.exe rev-parse "1c2ead96dfe52f7f0675161f025c2541ede93782^{commit}" # timeout=10 FATAL: Command "C:\Program Files (x86)\Git\bin\git.exe rev-parse "1c2ead96dfe52f7f0675161f025c2541ede93782^{commit}"" returned status code 128: stdout: 1c2ead96dfe52f7f0675161f025c2541ede93782^{commit} stderr: fatal: ambiguous argument '1c2ead96dfe52f7f0675161f025c2541ede93782^{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 "C:\Program Files (x86)\Git\bin\git.exe rev-parse "1c2ead96dfe52f7f0675161f025c2541ede93782^{commit}"" returned status code 128: stdout: 1c2ead96dfe52f7f0675161f025c2541ede93782^{commit} stderr: fatal: ambiguous argument '1c2ead96dfe52f7f0675161f025c2541ede93782^{commit}': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]'
