Hi there,
It looks like I might be getting bitten by the bug as mentioned at
http://jira.codehaus.org/browse/WAGON-253.
My symptoms were contents of known_hosts file were disappearing except
for the one server. As a result all other builds were failing as they
could not connect/ssh to source control host - we do use git.
mvn clean package cargo:redeploy site:site site:stage-deploy site:deploy
Above is the command hudson executes to deploy one war file on qa server
and deploy documentation and bunch of other stuff on documentation
server. Both cargo and site plugins seem to be wagon plugin and I found
multiple versions of wagon plugin in my hudson's local maven repository.
If I make known_hosts file readonly, build does fail with the error, can
not write to known_hosts file. Direct ssh or scp to remote hosts using
hudson as user, does work as expected as password less login is setup
correctly.
What is the best way to tell maven plugins to use the latest version of
wagon plugin. The bug mentioned above is resolved back in 2008/2009.
Using maven2, on ubuntu 11.04. Cargo plugin version is 1.1.2 explicitly
mentioned in POM, site plugin is not mentioned in POM at all so should
be using latest.
Last relevant lines from the build log
Using private key: /var/lib/hudson/.ssh/id_rsa
scp://wiki/var/www/docs/staging/ - Session: Connection refused
scp://wiki/var/www/docs/staging/ - Session: Disconnecting
scp://wiki/var/www/docs/staging/ - Session: Disconnected
[HUDSON] Archiving disabled - not archiving /var/lib/hudson/jobs/FiPort QA
deployer/workspace/pom.xml
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error uploading site
Embedded error: Connection aborted - failed to write to known_hosts. Reason:
/var/lib/hudson/.ssh/known_hosts (Permission denied)
Regards,
Niranjan
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
