Yes using Jenkins credentials.. Same working in Jenkins 1.6 running on Tomcat server running on windows. But failing Jenkins 2.0 running as a windows service.
Thanks. On Sat, Apr 8, 2017 at 10:37 AM, Mark Waite <[email protected]> wrote: > That message usually means that the authentication failed for the "git > ls-remote" call. > > If the repository requires credentials, then you'll need to define the > credential in the Jenkins credentials, and use that credential in the job > definition. > > Note that https git URL's need a username / password credential, not a > private key credential. > > Mark Waite > > On Sat, Apr 8, 2017 at 8:12 AM Simba K <[email protected]> wrote: > >> Thank you All for sharing thoughts. ..Branch actually exists.. But when i >> use option to poll the repo hourly, I see below error msg in logs. >> >> >> using GIT_ASKPASS to set credentials XXXX >> > git.exe ls-remote -h https://git.URLXXXX.git # timeout=10 >> Unexpected ls-remote output line '' >> [poll] Couldn't get remote head revision >> Done. Took 0.15 sec >> >> >> >> >> On Monday, April 3, 2017 at 3:08:22 AM UTC-4, Fritz Elfert wrote: >> >> Replies inline >> >> On 03.04.2017 00:08, Mark Waite wrote: >> > >> > >> > On Sun, Apr 2, 2017 at 3:23 PM Fritz Elfert <[email protected] >> > <mailto:[email protected]>> wrote: >> > >> > On 02.04.2017 22:35, Mark Waite wrote: >> > > That message usually means that the repository in the workspace >> > does not >> > > contain a reference named "master" or named "origin/master". >> That >> > is a >> > > surprise, since most repositories include a master branch. >> > >> > If the git plugin has this requirement, then this assumption is a >> bug. >> > There is no obligation at all to have a branch called "master". In >> fact, >> > at my employer, the default branch is called "devel" instead. >> > >> > >> > The git plugin does not have any requirement that there be a branch >> > named master. >> [...] >> >> Thanks for making that clear. >> >> Cheers >> -Fritz >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit https://groups.google.com/d/ >> msgid/jenkinsci-users/303ec8af-42b9-4df2-914a- >> 4a2c07064329%40googlegroups.com >> <https://groups.google.com/d/msgid/jenkinsci-users/303ec8af-42b9-4df2-914a-4a2c07064329%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Users" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/jenkinsci-users/WFWUJAO1oNc/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/jenkinsci-users/CAO49JtFW5GDvvXPi6HnFQPnQ6HpvR > %2BFr%3DorT8ieWKhOkE7-jTg%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFW5GDvvXPi6HnFQPnQ6HpvR%2BFr%3DorT8ieWKhOkE7-jTg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAN%2BocjVAv-hKue1-a2GrFFcpdJkYbG9Dh0eFXjLG4m1mq41gLQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
