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, 2013 4:42:56 PM UTC+1, teilo wrote: > > 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 be run as this jenkins user. > > > On Friday, 4 January 2013 15:32:55 UTC, Bjørn Water wrote: >> >> 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 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 info >>> svn+ssh://yourserver/path/to/repo ? >>> >>> On Friday, 4 January 2013 14:46:40 UTC, Bjørn Water wrote: >>>> >>>> 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 Friday, January 4, 2013 3:28:46 PM UTC+1, teilo wrote: >>>>> >>>>> 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 working >>>>> >>>>> /James >>>>> >>>>> On Friday, 4 January 2013 14:19:31 UTC, 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 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] >>>>>> ------------------------------------------------------------------------ >>>>>> [INFO] Unable to commit files >>>>>> Provider message: >>>>>> The svn command failed. >>>>>> Command output: >>>>>> Host key verification failed. >>>>>> svn: Commit failed (details follow): >>>>>> svn: To better debug SSH connection problems, remove the -q option from >>>>>> 'ssh' in the [tunnels] section of your Subversion configuration file. >>>>>> svn: Network connection closed unexpectedly >>>>>> >>>>>> [INFO] >>>>>> ------------------------------------------------------------------------ >>>>>> [INFO] Trace >>>>>> org.apache.maven.BuildFailureException: Unable to commit files >>>>>> Provider message: >>>>>> The svn command failed. >>>>>> Command output: >>>>>> Host key verification failed. >>>>>> svn: Commit failed (details follow): >>>>>> svn: To better debug SSH connection problems, remove the -q option from >>>>>> 'ssh' in the [tunnels] section of your Subversion configuration file. >>>>>> svn: Network connection closed unexpectedly >>>>>> >>>>>> at >>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:715) >>>>>> at >>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569) >>>>>> at >>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539) >>>>>> at >>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) >>>>>> at >>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284) >>>>>> at >>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) >>>>>> at >>>>>> org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:65) >>>>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) >>>>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) >>>>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) >>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>>>>> at >>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >>>>>> at >>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >>>>>> at java.lang.reflect.Method.invoke(Method.java:597) >>>>>> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) >>>>>> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) >>>>>> at hudson.maven.agent.Main.launch(Main.java:185) >>>>>> at hudson.maven.MavenBuilder.call(MavenBuilder.java:153) >>>>>> at hudson.maven.Maven2Builder.call(Maven2Builder.java:79) >>>>>> at hudson.maven.Maven2Builder.call(Maven2Builder.java:55) >>>>>> at hudson.remoting.UserRequest.perform(UserRequest.java:118) >>>>>> at hudson.remoting.UserRequest.perform(UserRequest.java:48) >>>>>> at hudson.remoting.Request$2.run(Request.java:326) >>>>>> at >>>>>> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) >>>>>> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) >>>>>> at java.util.concurrent.FutureTask.run(FutureTask.java:138) >>>>>> at >>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) >>>>>> at >>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) >>>>>> at java.lang.Thread.run(Thread.java:662) >>>>>> Caused by: org.apache.maven.plugin.MojoFailureException: Unable to >>>>>> commit files >>>>>> Provider message: >>>>>> The svn command failed. >>>>>> Command output: >>>>>> Host key verification failed. >>>>>> svn: Commit failed (details follow): >>>>>> svn: To better debug SSH connection problems, remove the -q option from >>>>>> 'ssh' in the [tunnels] section of your Subversion configuration file. >>>>>> svn: Network connection closed unexpectedly >>>>>> >>>>>> at >>>>>> org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:287) >>>>>> at >>>>>> org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:237) >>>>>> at >>>>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) >>>>>> at >>>>>> hudson.maven.agent.PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java:182) >>>>>> at >>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) >>>>>> ... 28 more >>>>>> Caused by: >>>>>> org.apache.maven.shared.release.scm.ReleaseScmCommandException: Unable >>>>>> to commit files >>>>>> Provider message: >>>>>> The svn command failed. >>>>>> Command output: >>>>>> Host key verification failed. >>>>>> svn: Commit failed (details follow): >>>>>> svn: To better debug SSH connection problems, remove the -q option from >>>>>> 'ssh' in the [tunnels] section of your Subversion configuration file. >>>>>> svn: Network connection closed unexpectedly >>>>>> >>>>>> at >>>>>> org.apache.maven.shared.release.phase.AbstractScmCommitPhase.checkin(AbstractScmCommitPhase.java:168) >>>>>> at >>>>>> org.apache.maven.shared.release.phase.AbstractScmCommitPhase.performCheckins(AbstractScmCommitPhase.java:148) >>>>>> at >>>>>> org.apache.maven.shared.release.phase.ScmCommitPreparationPhase.runLogic(ScmCommitPreparationPhase.java:75) >>>>>> at >>>>>> org.apache.maven.shared.release.phase.AbstractScmCommitPhase.execute(AbstractScmCommitPhase.java:79) >>>>>> at >>>>>> org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:203) >>>>>> at >>>>>> org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:140) >>>>>> at >>>>>> org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:103) >>>>>> at >>>>>> org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:279) >>>>>> ... 32 more >>>>>> >>>>>> >>>>>> >>>>>> I have already tried deleting my host key and requested a new one by >>>>>> doing a ssh directly from the server. >>>>>> >>>>>> But still giving an error. >>>>>> >>>>>> >>>>>> Anyone who knows what this error could be? >>>>>> >>>>>> >>>>>> Thanks in advance, >>>>>> >>>>>> Bjørn >>>>>> >>>>>>
