Hmm, I'm now having the same issue as this guy http://groups.google.com/group/jenkinsci-users/t/b965e844d7cab6cf
It seems to me as if its failing to install 1.39 and reverts back to the "default" of 1.34 On May 9, 3:41 pm, Chemmo <che...@gmail.com> wrote: > 1.37 I think, does the new one not use this xml file? > > On May 9, 3:03 pm, Chemmo <che...@gmail.com> wrote: > > > > > Hi, > > > I run Jenkins under a username which is used only by Jenkins from > > linux. I have previously entered my own (windows) credentials for > > proxy access when I need to update Jenkins/plugins, etc but have since > > removed the entry from the advanced tab of the update centre. I > > noticed my username was specified in the above file, so I deleted the > > file hoping it would not appear again, however it has come back again > > > Possibly unrelated, but I think this is causing problems where I > > cannot use svn with the Jenkins user. The user's credentials seem to > > be invalidated / corrupted by Jenkins (I see authentication failed > > errors after a number of hours) - I have proven this by changing the > > permissions for the users ~/.subversion/auth/svn.simple folder and > > contents so that it cannot be changed except by the root user. After > > doing this my problems disappeared, but it is not an ideal solution - > > for example, if I want to commit something in a shell script under > > this user I get the error: > > > svn: E204899: Cannot create new file '/home/<domain>/ > > <user>/.subversion/auth/svn.simple/auth.<some hex code>.tmp': > > Permission denied > > > Has anyone experienced something similar to this? > > > Thanks > > > David- Hide quoted text - > > - Show quoted text -
