Can you provide the output of git ls-remote YOUR_GIT_REPO_URL? - feel free to remove any sensitive branch names.
Also, one of the user had a similar issue which had to do with account permissions. You can check here - https://groups.google.com/d/msg/go-cd/wuZhknPKUag/sqtwEPoPAwAJ On Mon, Sep 24, 2018 at 12:25 PM Rasih ÇAĞLAYAN <[email protected]> wrote: > Hi. > > I checked it, i am sure bitbucket private repo is not empty. > Also same configuration works well on another GOCD server. I am trying to > seperate it to another server. This error occurs in new one. > > Thanks > > > 24 Eyl 2018 Pzt, saat 21:10 tarihinde Ankit Srivastava < > [email protected]> şunu yazdı: > >> Hi, >> >> Can you check and make sure the repo is not empty (maybe no commit yet). >> You get the same error when repo is empty. Refer below: >> >> [image: Inline image 1] >> >> On Wed, Sep 19, 2018 at 10:13 AM Rasih ÇAĞLAYAN <[email protected]> >> wrote: >> >>> Hi. >>> >>> After check connection feature "hang" i started pipeline and got >>> following error. >>> Any idea ? >>> >>> >>> - Could not trigger pipeline 'test-api-build'19 Sep, 2018 at >>> 20:24:07 Local Time >>> >>> Material update failed for material 'test-api-repository' because: >>> Error performing command: --- Command --- git rev-parse --abbrev-ref HEAD >>> --- Environment --- {GIT_ALLOW_PROTOCOL=http:https:ssh:git:file:rsync} >>> --- >>> INPUT ---- --- EXIT CODE (128) --- --- STANDARD OUT --- HEAD --- STANDARD >>> ERR --- STDERR: fatal: ambiguous argument 'HEAD': unknown revision or >>> path >>> not in the working tree. STDERR: Use '--' to separate paths from >>> revisions, >>> like this: STDERR: 'git <command> [<revision>...] -- [<file>...]' --- . >>> Cause: Error performing command: --- Command --- git rev-parse >>> --abbrev-ref >>> HEAD --- Environment --- >>> {GIT_ALLOW_PROTOCOL=http:https:ssh:git:file:rsync} >>> --- INPUT ---- --- EXIT CODE (128) --- --- STANDARD OUT --- HEAD --- >>> STANDARD ERR --- STDERR: fatal: ambiguous argument 'HEAD': unknown >>> revision >>> or path not in the working tree. STDERR: Use '--' to separate paths from >>> revisions, like this: STDERR: 'git <command> [<revision>...] -- >>> [<file>...]' --- >>> >>> >>> 19 Eylül 2018 Çarşamba 19:57:04 UTC+3 tarihinde Rasih ÇAĞLAYAN yazdı: >>>> >>>> Hi. >>>> >>>> I am using 18.9 version of GOCD >>>> >>>> I have 2 servers; win 2012 R2 x64 64 GB 32 core >>>> GOCD bundled java version installed on both. >>>> >>>> Server A working great. >>>> >>>> But Server B hanging on "Check Connection" on material configuration >>>> with exact same GOCD configuration (i backed-up and restored files from >>>> Server A to Server B GOCD) >>>> >>>> I can use git repo without using password; i mean i already type >>>> credentials before and git console is not asking again when i clone private >>>> repos. >>>> >>>> Questions >>>> >>>> 1. Why GOCD has no option to store git user name and password for CI-CD >>>> works even this process blocks many users ? >>>> >>>> 2. How can i store git user credentials on windows ? Am i doing >>>> something wrong ? How can i test it tı get understood i am doing right >>>> about git configuration for GOCD >>>> >>>> 3. Why GOCD does not offer feed back after i press "check connection" >>>> button on material configuration ? I dont have any error so how can i fix >>>> it if there was no error feedback ? >>>> >>>> As a result if i have to create git configuration correctly for GOCD, >>>> can you please explain how can i store my git credentials on windows step >>>> by step ? I found some documents and applied them; nothing changed. So i >>>> need >>>> >>>> 1. How to store git credentials on windows for future use (without >>>> asking password for GOCD) step by step ? (if you know any stable document >>>> please share url) >>>> 2. How to test it to get understood am i doing right or not. >>>> >>>> I am not native English speaker so if is there any mistake; sorry. >>>> >>>> Thanks >>>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "go-cd" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "go-cd" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > -- > You received this message because you are subscribed to the Google Groups > "go-cd" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
