SVN "Unable to commit files"
shevett
I'm at a loss to figure out how to fix it. I recently had a couple
maven repos update, and now I can no longer do releases via Jenkins.
When I do the 'schedule a maven release', the build (which had been
doing checkin-triggered builds just fine) fails here:
[INFO] Executing: svn --non-interactive commit --file /tmp/maven-
scm-1482906137.commit --targets /tmp/maven-scm-7392633810201830294-
targets
[INFO] Working directory: /var/lib/hudson/hudson.stonekeep.com/jobs/
congo-v2/workspace/trunk
[JENKINS] Archiving /var/lib/hudson/hudson.stonekeep.com/jobs/congo-v2/
workspace/trunk/pom.xml to /var/lib/hudson/hudson.stonekeep.com/jobs/
congo-v2/modules/com.stonekeep.congo$congo/builds/2011-07-11_15-49-26/
archive/com.stonekeep.congo/congo/2.1.0.1-SNAPSHOT/congo-2.1.0.1-
SNAPSHOT.pom
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Unable to commit files
Provider message:
The svn command failed.
Command output:
svn: Commit failed (details follow):
svn: OPTIONS of 'http://svn.stonekeep.com/svn/congo/v2/trunk':
authorization failed (http://svn.stonekeep.com)
My understanding is this is due to credentials against SVN either
being overwritten or not supplied. The problem is, I don't know how
to supply them - if I go through the Jenkins configurations creen, at
no point am I prompted with a username that is allowed to commit
against the repository - which is necessary for a build release (since
it modifies the pom.xml with a new revision number, and checks it back
into SVN.
Can someone help me find out where to supply the appropriate
credentials and get my release system back up and running?
Thank you!
-d
Matthew...@diamond.ac.uk
To get the credentials saved, simply log on using the account that Jenkins runs under, and then do any svn operation that requires credentials (specifying --username if required, and making sure you DON'T specify --non-interactive) - a checkout or commit, and respond that you want the credentials saved.
First, look in ~/.subversion/auth/svn.simple, and delete any files that have a username, but no password.
Matthew
--
This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
shevett
> What version of the subversion plugin are you using? The only good one (for us, anyhow) is 1.26.
> To get the credentials saved, simply log on using the account that Jenkins runs under, and then do any svn operation that requires credentials (specifying --username if required, and making sure you DON'T specify --non-interactive) - a checkout or commit, and respond that you want the credentials saved.
>
> First, look in ~/.subversion/auth/svn.simple, and delete any files that have a username, but no password.
how to do an svn setup just by hand as the tomcat55 user (which is
what runs the builds). I've tried entering in the credentials on the
Configure page (if you hit the ? next to the SVN setup, you an
manually enter the credentials there), but they don't seem to get
saved anywhere?
Current build does this:
[INFO] Executing: svn --non-interactive commit --file /tmp/maven-
[INFO] Working directory: /var/lib/hudson/hudson.stonekeep.com/jobs/
congo-v2/workspace/trunk
[JENKINS] Archiving /var/lib/hudson/hudson.stonekeep.com/jobs/congo-v2/
workspace/trunk/pom.xml to /var/lib/hudson/hudson.stonekeep.com/jobs/
SNAPSHOT.pom
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
Provider message:
The svn command failed.
Command output:
svn: Commit failed (details follow):
svn: OPTIONS of 'http://svn.stonekeep.com/svn/congo/v2/trunk':
authorization failed (http://svn.stonekeep.com)
builds I've kicked out have been copies of snapshot builds. Ew.
Dave Shevett
> What version of the subversion plugin are you using? The only good
> one (for us, anyhow) is 1.26.
1.28.
> To get the credentials saved, simply log on using the account that
> Jenkins runs under, and then do any svn operation that requires
> credentials (specifying --username if required, and making sure you
> DON'T specify --non-interactive) - a checkout or commit, and respond
> that you want the credentials saved.
I can't seem to get myself to 'be' that user. sudo su - tomcat55 just
returns back to myself. However, I was able to go to Hudson->Configure
project, er jenkins... whatever), click on teh [?] next to SVN repo, and
buried in there is a link for specifying new credentials. I'll that now.
> First, look in ~/.subversion/auth/svn.simple, and delete any files that have a username, but no password.
I deleted a long hex-named file from there.
I'll let folks know how it works.
-d