On 29.09.2017 09:11, Dirk Heinrichs wrote:
This looks to me as if you were trying to run the git commands from an
"Execute Windows Batch" step in your Jenkins job. It's far easier to
simply use the Git plugin to do the job together with the SSH key you
provided to Jenkins via "Manage Jenkins"
Am 28.09.2017 um 16:54 schrieb Andreas Tscharner:
> Hello World,
>
> I have the following setup:
>
> git Server: Debian Linux 9.1
> Jenkins master: Debian Linux 9.1
> Jenkins agent: Windows 7
>
> I created a user on the git server for building, it is called "build".
> I also have created a ssh key-
On 28.09.2017 17:12, Mark Waite wrote:
I don't use putty and plink in my Windows based test setup for the git
plugin. Can you share the key reasons you chose those non-default
installation options?
IMHO PuTTY is THE ssh client for Windows (first hit with Google ("ssh
for Windows"), used by
I don't use putty and plink in my Windows based test setup for the git
plugin. Can you share the key reasons you chose those non-default
installation options?
Mark Waite
On Thu, Sep 28, 2017 at 8:55 AM Andreas Tscharner
wrote:
> Hello World,
>
> I have the following setup:
>
> git Server: Debi
Hello World,
I have the following setup:
git Server: Debian Linux 9.1
Jenkins master: Debian Linux 9.1
Jenkins agent: Windows 7
I created a user on the git server for building, it is called "build". I
also have created a ssh key-pair for that user. The public key is in the
authorized_keys fil
