Maven Release Plugin Fails to release. Svn CHECKOUT failed
https://stackoverflow.com/questions/4218369
-
26-09-2019 - |
italiano
english
français
española
中国
日本の
العربية
Deutsch
한국어
Português
RussianQuestion
Hi I'm trying to use the maven release plug-in on Hudson. The build succeeds and after then, when hudson tries to release the project, it fails with the following error.
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Unable to commit files
Provider message:
The svn command failed.
Command output:
svn: Commit failed (details follow):
svn: CHECKOUT of '/svn/projects/!svn/ver/82706/some/path/buildconfig/configuration/pom.xml': authorization failed: Could not authenticate to server: rejected Basic challenge (http://xx.xxx.xx.xx)
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2 minutes 17 seconds
[INFO] Finished at: Thu Nov xx 12:25:31 CST xxxx
[INFO] Final Memory: 22M/88M
[INFO] ------------------------------------------------------------------------
channel stopped
Finished: FAILURE
what I'm missing here. I have seen a few articles related to this on stackoverflow.But, they are not related to CHECKOUT.
I think its a problem with SVN, and because of that, maven cannot proceed. The person running the hudson can do the basic SVN commands on the command line.
Any help related to this will be appreciated.
Solution 2
This problem was solved by asking the person who owned the hudson process to do the release. It worked fine then. The problem we have is there is no shared user for hudson. The person who installed it owns it.
When we move to the new hudson box, we have to create a dedicated hudson user.
OTHER TIPS
The person running the hudson can do the basic SVN commands on the command line.
Does that also mean that the user Hudson is running as (most probably "hudson") can perform the svn commands? If not, you could check that by performing a sudo su hudson - and then trying the mvn release:prepare/perform commands.
