@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Bjørn Water
Sent: 07 January 2013 09:43
To: jenkinsci-users@googlegroups.com
Subject: Re: Jenkins svn ssh / host key verification problems
So i have checked and the slave where i run my build process on does not
contain a host key.
So
So i have checked and the slave where i run my build process on does not
contain a host key.
So i suspect this slave also needs one?
On Friday, January 4, 2013 3:19:31 PM UTC+1, Bjørn Water wrote:
>
> So i am trying to use the M2-release plugin to release my project and push
> it to my nexus.
>
Anyone that has an idea? It is getting pretty anoying so far . Would love
to get this working because it seems very promosing
On Friday, January 4, 2013 3:19:31 PM UTC+1, Bjørn Water wrote:
>
> So i am trying to use the M2-release plugin to release my project and push
> it to my nexus.
> I can d
Yes i have checked both the user file wich is jenkins and the root and they
both contain .
Still think that it is very wierd that a checkout works and tagging it
works aswell but doing a release gives host problems.
Shouldn't checkout and tag give the same problem then?
On Friday, January 4, 20
are you sure you are looking in the correct file?
it should be in the home file of the user that the jenkins service runs as.
for the rpm the default (IIRC is ~jenkins/.ssh/known_hosts) - it may be
somewhere else depending on your container / launch /install method.
the svn commands also needs to
I have removed the host from the file and then ran it again.
There is no entry being made in that file so it does not override or writes
something to the known_hosts file
On Friday, January 4, 2013 3:54:09 PM UTC+1, teilo wrote:
>
> Jenkins tags using its inbuilt library (svnkit) as far as I am a
yes it is in var/lib/jenkins/.ssh thats is where our keys are already in
place
On Friday, January 4, 2013 4:09:53 PM UTC+1, Adam Tong wrote:
>
> Hi,
>
> Did you try copying the .ssh folder to the jenkins folder?
>
> I am using git but this solved the problem.
>
>
> On Fri, Jan 4, 2013 at 9:19
Hi,
Did you try copying the .ssh folder to the jenkins folder?
I am using git but this solved the problem.
On Fri, Jan 4, 2013 at 9:19 AM, Bjørn Water wrote:
> So i am trying to use the M2-release plugin to release my project and push
> it to my nexus.
> I can do svn checkout and i can even ta
Jenkins tags using its inbuilt library (svnkit) as far as I am aware so the
native ssh client doesn't get a look in.
to see if its overridden the entry just check ~/.ssh/known_hosts for an
entry for your server (after you removed it)
What happens if as the jenkins user on the slave you run svn
Hi James,
I have manually removed the entry from the file and then did a SSH command
again and accepted the certificate.
Still getting the same problems as before.
Is there a way to see if it overrides the entry?
Because it works when I tag it and that is also a commit right?
Thanks,
Bjørn
On
I have completely to opposite experience, native svn+ssh is so much simpler
than all other options!
The provider also says it only works with http/https so may not even be
much use (but then again documentation could just be out of date)
On Friday, 4 January 2013 14:32:35 UTC, domi wrote:
>
> W
We had lots of issues when using the cli subversion client for release builds,
therefore we moved to the svnjava provider and have no issues anymore:
http://code.google.com/a/apache-extras.org/p/maven-scm-provider-svnjava/
/Domi
On 04.01.2013, at 15:19, Bjørn Water wrote:
> So i am trying to us
Hi Bjørn
As the jenkins user on the slave ssh to the svn server and accept its key.
Depending on your ssh clinet it may override the entry stored in
~/.ssh/known_hosts or may not. (if not then remove the entry manually from
this file and retry with the ssh command)
That should get it work
So i am trying to use the M2-release plugin to release my project and push
it to my nexus.
I can do svn checkout and i can even tag my build and see it in my repo
but when i try to do mvn release:prepare after a succesfull build i get an
error
[ERROR] BUILD FAILURE[INFO]
--
14 matches
Mail list logo
