-
Bug
-
Resolution: Won't Fix
-
Blocker
-
None
-
Platform: All, OS: All
Executing a release build using maven-release hudson hangs performing CVS
update. Nothing to see in logs, output is always the same:
Started by user shofmann
Baue auf Master
[maven-release-test] $ cvs -Q -z3 -d :ext:<user@cvs.de>:/home/cvsroot co -P -d
workspace -D "Thursday, November 5, 2009 9:36:23 AM UTC" maven-release-test
$ computing changelog
Parsing POMs
[workspace] $ /usr/lib/jvm/java-1.5.0-sun/bin/java -cp
/opt/hudson/plugins/maven-plugin/WEB-INF/lib/maven-agent-1.332.jar:/opt/apache-maven-2.2.0/boot/classworlds-1.1.jar
hudson.maven.agent.Main /opt/apache-maven-2.2.0
/var/run/hudson/war/WEB-INF/lib/remoting-1.332.jar
/opt/hudson/plugins/maven-plugin/WEB-INF/lib/maven-interceptor-1.332.jar 35593
/opt/hudson/plugins/maven-plugin/WEB-INF/lib/maven2.1-interceptor-1.2.jar
<===[HUDSON REMOTING CAPACITY]===>channel started
Executing Maven: -B -f /opt/hudson/jobs/maven-release-test/workspace/pom.xml
-Dresume=false -P integration release:prepare release:perform
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'release'.
[INFO] ------------------------------------------------------------------------
[INFO] Building maven-release-test
[INFO] task-segment: [release:prepare, release:perform] (aggregator-style)
[INFO] ------------------------------------------------------------------------
[INFO] [release:prepare
]
[INFO] Verifying that there are no local modifications...
[INFO] Executing: /bin/sh -c cd /opt/hudson/jobs/maven-release-test/workspace &&
cvs -z3 -f -d :ext:<user@cvs>:/home/cvsroot -n -q update -d
[INFO] Working directory: /opt/hudson/jobs/maven-release-test/workspace
At CVS server I see that three SSH sessions were opended and closed for hudson
user but fourth session will never be closed... Normal builds work fine.
[JENKINS-4783] Hudson hangs performing maven release build with CVS
sebhof
added a comment - Thanks a lot - adding the property
-Dmaven.scm.provider.cvs.implementation=cvs_native solved this for me.
Perhaps cvs_native should be used by default?
sebhof
added a comment - Thanks a lot - adding the property
-Dmaven.scm.provider.cvs.implementation=cvs_native solved this for me.
Perhaps cvs_native should be used by default? Strange - the above log seems like it is using the native cvs?
[INFO] Executing: /bin/sh -c cd /opt/hudson/jobs/maven-release-test/workspace && cvs -z3 -f -d :ext:<user@cvs>:/home/cvsroot -n -q update -d
I Haven't used CSV in years - and have never used maven+cvs so I don't know what problems this change cause
closing as it's more a maven/cvs interaction issue.
There is a valid workaround but this requires cvs to be installed on all the salves, and some users might not want that and to stick with the java implementation.
Updated the FAQ on the wiki incase others stumble upon this
I had the same problem on Windows 2k and was able to solve it by adding the
following two properties (CVS_RHS must be set to a valid ssh command):
-Dusername=myuserid -Dmaven.scm.provider.cvs.implementation=cvs_native