Adam Retter writes:
>
>
>
> Hi Jan,
>
> Thanks for your reply I have finally solved this, unfortunately it was
not as simple as I hoped (probably due to the fact our platform is on
Windows Server).
>
> The point you raised below, gave me a good hint -
> Run a simply svn command like list/i
Adam Retter writes:
>
>
>
> Hi Jan,
>
> Thanks for your reply I have finally solved this, unfortunately it was
not as simple as I hoped (probably due to the fact our platform is on
Windows Server).
>
> The point you raised below, gave me a good hint -
> Run a simply svn command like list/i
Hi Jan,
Thanks for your reply I have finally solved this, unfortunately it was not
as simple as I hoped (probably due to the fact our platform is on Windows
Server).
The point you raised below, gave me a good hint -
>- Run a simply svn command like list/info/whatever from a
>shell/c
Hi Adam,
Your server is already using a certificate, so this is nothing you have to
worry about anymore in order to get Jenkins running ;)
Install the server certificate on the machine running Jenkins in the
trusted cert store.
Note you may have to install it in various stores.
- ssh to the
Our Subversion server is operating over HTTPS and works fine typically form
the command line. We are using a self-signed certificate and the first time
we do an 'svn co' locally we have to of course permanently accept the
certificate. However I cannot seem to get Jenkins to work with our
Subver
