A svn credentials question

4,508 views
Skip to first unread message

David Aldrich

unread,
Nov 20, 2014, 11:32:38 AM11/20/14
to jenkins...@googlegroups.com

Hi

 

In one of my Jenkins jobs, I want to run ‘svn ls’ against the repository from which Jenkins has checked out its working copy.  My svn client is compatible with Jenkins’ svn working copy format. 

 

I get Jenkins to check out the working copy and then run some svn commands in the build steps.

 

If I run ‘svn status’ it works fine.  But with ‘svn ls’ I see:

 

C:\Jenkins\workspace\tagLog>svn ls --verbose --trust-server-cert  
svn: E215004: Authentication failed and interactive prompting is disabled; see the --force-interactive option
svn: E215004: Unable to connect to a repository at URL <repo url>
svn: E215004: No more credentials or we tried too many times.
Authentication failed
 

Please can anyone suggest how to make this work?

 

Best regards

 

David

 

Jan Seidel

unread,
Nov 21, 2014, 4:07:25 AM11/21/14
to jenkins...@googlegroups.com, david....@emea.nec.com
Remove the --force-interactive

That forces user input like username, then password no matter if you have stored the credentials or not

David Aldrich

unread,
Nov 21, 2014, 5:28:28 AM11/21/14
to Jan Seidel, jenkins...@googlegroups.com

Hi Jan

 

The actual command I used was:

 

svn ls --verbose --non-interactive --trust-server-cert https:<myurl>

 

David

Jan Seidel

unread,
Nov 21, 2014, 9:51:44 AM11/21/14
to jenkins...@googlegroups.com, david....@emea.nec.com
Hi,

would be nice to know which dialog is popping up.
Try to run the command normal without fancy switches.
If you use a command line svn client try the command straight away from the CLI in a DOS box.
I assume it is asking you, if you want to add the server certificate.

If you want to run it automated, prepend a "| y" (pipe and y, without qoutes to your command) and run it once.

Take care

David Aldrich

unread,
Nov 21, 2014, 9:56:24 AM11/21/14
to Jan Seidel, jenkins...@googlegroups.com

Thanks for your reply.

 

After trying lots of things, I moved the job from a Windows slave to a Linux slave and it worked fine ;-)

 

David

Reply all
Reply to author
Forward
0 new messages