I have this problem, too. I assume there must be a more modern solution to
the problem of configuration management and tracking, because this is
shockingly bad.
On Thursday, May 14, 2015 at 5:07:41 PM UTC-7, dougla...@gmail.com wrote:
>
> I couldn't find any way of entering Git credentials that
Nope, still depending on the under-the-bonnet `credential-helper`
work-around, sorry.
--
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 jenkinsci-users+unsubscr.
Nope, still depending on the under-the-bonnet `credential-helper`
work-around, sorry.
On Thursday, 28 May 2015 03:15:53 UTC+12, Costya Regev wrote:
>
> Hi ,
>
> Did you manage to solve this problem ?
>
> On Friday, May 15, 2015 at 3:07:41 AM UTC+3, dougla...@gmail.com wrote:
>>
>> I couldn't find
Hi ,
Did you manage to solve this problem ?
On Friday, May 15, 2015 at 3:07:41 AM UTC+3, dougla...@gmail.com wrote:
>
> I couldn't find any way of entering Git credentials that the
> scm-sync-configuration would use. Am I missing something?
>
> I have created credentials for our git server, and
I couldn't find any way of entering Git credentials that the
scm-sync-configuration would use. Am I missing something?
I have created credentials for our git server, and I am able to use these
to check out sources from the server as part of a job (over http). The git
plugin correctly generates