-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
master OS: ubuntu 8.4 LTS
slave OS: Linux *** 2.6.9-55.0.2.ELhugemem #1 SMP Tue Jun 12 18:11:10 EDT 2007 i686 i686 i386 GNU/Linux
Jenkins: 1.406
subversion: 1.5.3 with https
2: authenticate personal svn account on linux slave. "non-interactive" option works.
3: Source Code Management choose SVN and point to a URL with same svn root.
4: build step will checkout source codes via svn with account already authorized.
5: execute the job, at the same time check the authentication on linux client.
6: while Source Code Management step start, the svn authentication on linux client became invalid.
7: build step will definitely failed with error. log For example:
+ svn list https://svne1.access.domainname.com/isource/svnroot/test-isource-auth --non-interactive
svn: OPTIONS of 'https://svne1.access.domainname.com/isource/svnroot/test-isource-auth': authorization failed (https://svne1.access.domainname.com)
8: downgrade subversion to 1.17 and reconnect the slave will fix the problem.
- duplicates
-
JENKINS-8059 Subversion Plugin does break native svn command line authentication, credentials missing after rewriting auth cache file
- Resolved