subject:"\[JIRA\] $JENKINS\-32167$ ISVNAuthentication provider did not provide credentials"

Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Yates commented on  JENKINS-32167  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ISVNAuthentication provider did not provide credentials   
 

  
 
 
 
 

 
 Similar to this issues JENKINS-37642  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Yates updated  JENKINS-32167  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Nevermind the description doesn't match my issue.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-32167  
 
 
  ISVNAuthentication provider did not provide credentials   
 

  
 
 
 
 

 
Change By: 
 Keith Yates  
 
 
Status: 
 Reopened Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Yates reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 I'm experiencing this on 2.11.1 I saw a related ticket that state it might be related to xUnit plugin also being installed if that helps.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-32167  
 
 
  ISVNAuthentication provider did not provide credentials   
 

  
 
 
 
 

 
Change By: 
 Keith Yates  
 
 
Resolution: 
 Fixed  
 
 
Status: 
 Resolved Reopened  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

2018-04-20 Thread joergen.vonbar...@minebea-intec.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Yates updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-32167  
 
 
  ISVNAuthentication provider did not provide credentials   
 

  
 
 
 
 

 
Change By: 
 Keith Yates  
 
 
Comment: 
 I'm experiencing this on 2.11.1I saw a related ticket that state it might be related to xUnit plugin also being installed if that helps.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jørgen von Bargen commented on  JENKINS-32167  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ISVNAuthentication provider did not provide credentials   
 

  
 
 
 
 

 
 I just wanted to point to https://issues.jenkins-ci.org/browse/JENKINS-45801 There are two simple bash scripts to reproduce the defect (or at least a variant of it). Please feel free to include theses scripts into your build system to verify the defect or it's fix.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

2018-04-18 Thread andrew.lu...@l3t.com (JIRA)

Title: Message Title

Andrew Lucas commented on JENKINS-32167

Re: ISVNAuthentication provider did not provide credentials

You closed JENKINS-31455 as a duplicate to this one. If this one ever gets worked, be sure to address that it is seen when using external svn references in a build. The first build fails with the authentication error, then the next completes. The cause of the build is lost to the second build, and two builds have to occur. 31455 had some comments that might be useful to keep track of: Stephen McCants added a comment - 2018-02-13 13:59 Dimitar Sakarov, as stated in JENKINS-32167, there is no owner or maintainer of this plugin. There is a workaround provided in comments under JENKINS-32167. Jesse Glick provided some better feedback code, but I don't think that has ever shipped. I looked at it and wrote a test case demonstrating the problem, but solving it was too complicated for the time I could devote to it. I don't think anything has changed since then. Wish someone would step up and fix it for us users, but I'm not expecting it until the SVN plugin is totally busted.

Add Comment

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

2018-04-09 Thread matthews.grochowal...@ge.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt Grochowalski commented on  JENKINS-32167  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ISVNAuthentication provider did not provide credentials   
 

  
 
 
 
 

 
 Liyaa submitted a pull request to fix this issue: https://github.com/jenkinsci/subversion-plugin/pull/212  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

2018-04-05 Thread e...@wp.pl (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maciej Jaros edited a comment on  JENKINS-32167  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ISVNAuthentication provider did not provide credentials   
 

  
 
 
 
 

 
 I used [~advorsky73] solution from [#comment-246389] since January 2016. Didn't update Jenkins (still on 1.x), but 2.5.7 version of SVN plugin with that fix works fine. All features seem to work correctly (checkout works with and without externals, changes show up in the build, passing credentials work). Most of the builds in installation of my current company use SVN. And there are many externals in repos used.  It would seem the workaround is a valid solution (as there has been no other solution present) and the exception is a false negative somehow... Could someone push the solution to the official repo and run some automated tests (if there are  ones first  any for  this one).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

2018-04-05 Thread e...@wp.pl (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maciej Jaros commented on  JENKINS-32167  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ISVNAuthentication provider did not provide credentials   
 

  
 
 
 
 

 
 I used Alexander Dvorsky solution from comment-246389 since January 2016. Didn't update Jenkins (still on 1.x), but 2.5.7 version of SVN plugin with that fix works fine. All features seem to work correctly (checkout works with and without externals, changes show up in the build, passing credentials work). Most of the builds in installation of my current company use SVN. And there are many externals in repos used. It would seem the workaround is a valid solution (as there has been no other solution present) and the exception is a false negative somehow... Could someone push the solution to the official repo and run some automated tests (if there are ones first this one).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

2018-04-03 Thread stephen.mcca...@hcs.us.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen McCants commented on  JENKINS-32167  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ISVNAuthentication provider did not provide credentials   
 

  
 
 
 
 

 
 Edgars Batna, unfortunately no one owns or maintains this code, so there is no ETA.  Wish I had better news for all of us who are affected.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

2018-04-03 Thread mdea...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Edgars Batna commented on  JENKINS-32167  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ISVNAuthentication provider did not provide credentials   
 

  
 
 
 
 

 
 Any rough estimates for an ETA? More than half of builds are effectively background noise in our build system due to this.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

2017-03-28 Thread stephen.mcca...@hcs.us.com (JIRA)

Title: Message Title

Stephen McCants commented on JENKINS-32167

Re: ISVNAuthentication provider did not provide credentials

Jesse Glick, playing some with the unit test you created, I realized it is a different use case then the one I'm using in my production Jenkins environment. I have externals that point to the same SVN server and can use the same user id/password to get data from the externals and the main project. I've refactored your unit test into that situation with only one SVN server, but still two repositories - one using the other as an external. It almost passes without additionalCredentials. That resulted in a couple of thoughts:

The reason it almost passes is because it is lucky enough to find the defaultCredentials in RemotableSVNAuthenticationBuilderProvider.getBuilder(String realm) every step of the way until SubversionSCM.checkout(...) calls the BuildRevisionMapTask constructor, which always builds the defaultAuthProvider with a null location value. The null location means it won't have default credentials and must have additionalCredentials to succeed.

Should you ever be allowed to have no default credentials?
Should the code warn/error if there are no default credentials and no additional credentials? Maybe in the CredentialsSVNAuthenticationProviderImpl constructor?
Does it make sense to cache credentials against realms where they have previously worked? That would work around this problem without providing additional credentials that are duplicates of the default.

Would you be interested in my unit test (I'd polish it a little more before sending it along)?
I was tripped up in my production environment because of a difference in realms between a full qualified host name and an unqualfied hostname. That I provided additional credentials for the realm " Subversion repository", but it was looking for " Subversion repository" based on the way the external had been configured. It would be preferable if the final solution was smart enough to handle fully qualified host names, IP addresses and unqualified host names.

Add Comment

[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

2017-02-21 Thread jgl...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-32167  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ISVNAuthentication provider did not provide credentials   
 

  
 
 
 
 

 
 Found it—I was just missing anon-access = none, as noted here and elsewhere. With that the test passes, including changelog of externals using additionalCredentials. As an aside, if you get the password wrong for the main checkout, you get a cryptic “authentication cancelled” message, whereas a wrong password in additional credentials causes the externals to just quietly be omitted. Not sure if this is all just poor behavior in SVNKit or what.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

2017-02-21 Thread jgl...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-32167  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ISVNAuthentication provider did not provide credentials   
 

  
 
 
 
 

 
 Hmm, a have a test which is now producing a different error (but only from changelog calculation, not the actual update): 

 

hudson.util.IOException2: revision check failed on svn://…/trunk
	at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:208)
	at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:124)
	at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:725)
	at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:860)
	at …
Caused by: org.tmatesoft.svn.core.SVNAuthenticationException: svn: E220001: Item is not readable
	at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:68)
	at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:57)
	at org.tmatesoft.svn.core.internal.io.svn.SVNReader.handleFailureStatus(SVNReader.java:269)
	at org.tmatesoft.svn.core.internal.io.svn.SVNReader.parse(SVNReader.java:248)
	at org.tmatesoft.svn.core.internal.io.svn.SVNConnection.read(SVNConnection.java:276)
	at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.read(SVNRepositoryImpl.java:1311)
	at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.logImpl(SVNRepositoryImpl.java:843)
	at org.tmatesoft.svn.core.io.SVNRepository.log(SVNRepository.java:1038)
	at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:181)
	at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35)
	at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21)
	at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1235)
	at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294)
	at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:968)
	at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:873)
	at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:194)
	... 12 more
 

 Still trying to figure out what that might mean. JENKINS-27231?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

2017-02-14 Thread jgl...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-32167  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ISVNAuthentication provider did not provide credentials   
 

  
 
 
 
 

 
 Stefan Walter 

If I re-run the job then it works just fine.
 Well I would need to see the corresponding credentials-related log message in a successful build to compare. Mike Stolls appears to be referring to this line, consistent with a hypothesis that the checkout succeeds but changelog calculation fails while trying to contact the server a second time.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

2017-02-10 Thread mkai...@cit-ec.uni-bielefeld.de (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin Kaiser updated  JENKINS-32167  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-32167  
 
 
  ISVNAuthentication provider did not provide credentials   
 

  
 
 
 
 

 
Change By: 
 Martin Kaiser  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

2017-02-10 Thread mkai...@cit-ec.uni-bielefeld.de (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin Kaiser updated  JENKINS-32167  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-32167  
 
 
  ISVNAuthentication provider did not provide credentials   
 

  
 
 
 
 

 
Change By: 
 Martin Kaiser  
 
 
Status: 
 In  Review  Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

2017-02-10 Thread rrodgil.plat...@gmail.com (JIRA)

Title: Message Title

Romen Rodriguez-Gil edited a comment on JENKINS-32167

Re: ISVNAuthentication provider did not provide credentials

We are experiencing this issue as well.We have several jobs that use the Jenkins' subversion plugin and work fine, but our multibranch jobs throw InterruptedException (Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled).Could this be related to the externals issue that some users are reporting? We have not defined any externals ourselves. I wonder if Pipeline:Multibranch does internally, since we are only experiencing this with multibranch jobs. *Edit* - We have figured out how to solve our issue. In case it is useful for somebody else, what we did was to change the checkout line we had in our Jenkinsfile. Instead of passing all parameters (checkout([$class: 'SubversionSCM', additionalCredentials: [], excludedCommitMessages: '', excludedRegions: '', excludedRevprop: ','...) we simply use "checkout scm", which takes the default options. It seems to work fine now.

Add Comment

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)

[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

2017-02-09 Thread rrodgil.plat...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Romen Rodriguez-Gil commented on  JENKINS-32167  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ISVNAuthentication provider did not provide credentials   
 

  
 
 
 
 

 
 We are experiencing this issue as well. We have several jobs that use the Jenkins' subversion plugin and work fine, but our multibranch jobs throw InterruptedException (Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled). Could this be related to the externals issue that some users are reporting? We have not defined any externals ourselves. I wonder if Pipeline:Multibranch does internally, since we are only experiencing this with multibranch jobs.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

Title: Message Title


 
 
 
 

 
 
 

 
   
 Victor Ott updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-32167  
 
 
  ISVNAuthentication provider did not provide credentials   
 

  
 
 
 
 

 
Change By: 
 Victor Ott  
 
 
Attachment: 
 screenshot01.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

Title: Message Title


 
 
 
 

 
 
 

 
   
 Victor Ott updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-32167  
 
 
  ISVNAuthentication provider did not provide credentials   
 

  
 
 
 
 

 
Change By: 
 Victor Ott  
 
 
Attachment: 
 screenshot01.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

Title: Message Title


 
 
 
 

 
 
 

 
   
 Victor Ott commented on  JENKINS-32167  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ISVNAuthentication provider did not provide credentials   
 

  
 
 
 
 

 
 We experience this same issue, pure Linux environment: 
 
Linux x86_64, Kernel 3.0.101-65-default 
JDK8 64bit 
Jenkins ver. 2.19.4 
Subversion Plugin 2.7.1 
 All affected jobs have SVN checkouts with externals (externals pointing to relative locations, on same server). All SVN configured projects/jobs are matching the SVN realm. Adding a second credential to the checkout configurations, with exactly the same parameters as the first credential, can only be a test workaround, and I'll apply that to only two jobs. Here two examples of affected jobs: 
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

Title: Message Title


 
 
 
 

 
 
 

 
   
 Victor Ott updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-32167  
 
 
  ISVNAuthentication provider did not provide credentials   
 

  
 
 
 
 

 
Change By: 
 Victor Ott  
 
 
Attachment: 
 screenshot02.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

Title: Message Title


 
 
 
 

 
 
 

 
   
 Victor Ott updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-32167  
 
 
  ISVNAuthentication provider did not provide credentials   
 

  
 
 
 
 

 
Change By: 
 Victor Ott  
 
 
Attachment: 
 screenshot01.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

2017-02-08 Thread mike.sto...@gmail.com (JIRA)

Title: Message Title

Mike Stolls commented on JENKINS-32167

Re: ISVNAuthentication provider did not provide credentials

Coming back on to this. I ended up rebuilding the subversion plugin myself to try to address the issue. Not sure if this is the case for everyone, but my auth error appeared to come when building the changelog for externals. The problem appeared to be line ~131 of src/main/java/hudson/scm/SubversionChangeLogBuilder.java. When calling createAuthenticationProvider(build.getParent(), scm, null); when null is passed into this function it seems to crap out. I ended up passing in a ModuleLocation from just above: createAuthenticationProvider(build.getParent(), scm, scm.getLocations(env, build)[0]);. I've been running with the recompiled plugin for about a month now and i havent havent the same issue. To be honest, I have no idea about the auth workflow, it was just a stab in the dark. I figured i would mention it here as a place to look deeper into for a more official fix.

Add Comment

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)

[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

2017-02-08 Thread ber...@gmx.de (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Seifert commented on  JENKINS-32167  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ISVNAuthentication provider did not provide credentials   
 

  
 
 
 
 

 
 I would like to give an additional hint:  The transition from a failed checkout to a successful checkout requires alway the start of new build. I set up Jenkins to perform repeated scm checkouts in case of failure (currently 9 repeats), but always all subsequent checkout attempts after a failed checkout do also fail.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

2017-02-07 Thread sebastian.la...@de.mapal.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sebastian Lange edited a comment on  JENKINS-32167  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ISVNAuthentication provider did not provide credentials   
 

  
 
 
 
 

 
 I can confirm this. We encounter the same problems. All externals are on the same SVN-server. Nevertheless it breaks on first revision-check initialted build, but succeeds with the next build. Do not mind the binary stores on the SVN, just a convenience thing{code:java}...A N\libs\mysql\docs\INFO_BINA N\libs\mysql\docs\ChangeLogA N\libs\mysql\READMEAt revision 5113Hole 'http://10.*.*.*/svn/unit/path/RL-32' aus Revision -1 in Datei 'C:\Jenkins\N\libs\RL' AUN\libs\RL\RLn1.dllAUN\libs\RL\RLn2.dllAt revision 5113At revision  10752  5113 No changes for http://10.*.*.*/svn/unit/path/project since the previous buildorg.tmatesoft.svn.core.SVNCancelException: svn: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled. at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:723)Caused: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled.svn: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled. at org.tmatesoft.svn.core.internal.wc.SVNError{code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more

[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

2017-02-07 Thread sebastian.la...@de.mapal.com (JIRA)

Title: Message Title

Sebastian Lange commented on JENKINS-32167

Re: ISVNAuthentication provider did not provide credentials

I can confirm this. We encounter the same problems. All externals are on the same SVN-server. Nevertheless it breaks on first revision-check initialted build, but succeeds with the next build. Do not mind the binary stores on the SVN, just a convenience thing

...
A N\libs\mysql\docs\INFO_BIN
A N\libs\mysql\docs\ChangeLog
A N\libs\mysql\README
At revision 5113

Hole 'http://10.*.*.*/svn/unit/path/RL-32' aus Revision -1 in Datei 'C:\Jenkins\N\libs\RL'
AUN\libs\RL\RLn1.dll
AUN\libs\RL\RLn2.dll
At revision 5113

At revision 10752
No changes for http://10.*.*.*/svn/unit/path/project since the previous build
org.tmatesoft.svn.core.SVNCancelException: svn: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled.
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:723)
Caused: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled.
svn: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled.
at org.tmatesoft.svn.core.internal.wc.SVNError

Add Comment

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)

[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

2017-02-06 Thread stefan.wal...@lisec.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Stefan Walter commented on  JENKINS-32167  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ISVNAuthentication provider did not provide credentials   
 

  
 
 
 
 

 
 Jesse Glick, thanks for your suggestion, but everything is configured right. If I re-run the job then it works just fine. There is somehow an issue with externals. Jenkins seems to stop providing the configured credentials at some point. The issue is not the configuration, otherwise, it would always fail.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

2017-02-06 Thread jgl...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-32167  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ISVNAuthentication provider did not provide credentials   
 

  
 
 
 
 

 
 Stefan Walter 

The issue still persists even with snapshot 2.7.2.
 Of course, the PR only provides logging to make it clearer what is wrong, whether with your configuration or something else. 

 

Using sole credentials  in realm ‘ Your AD Username/Password for SVN’
 

 suggests that you have not configured any credentials, “additional” or primary.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

2017-02-03 Thread stefan.wal...@lisec.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Stefan Walter edited a comment on  JENKINS-32167  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ISVNAuthentication provider did not provide credentials   
 

  
 
 
 
 

 
 The issue still persists even with snapshot 2.7.2. {{ No changes for https://** since the previous buildUsing sole credentials  in realm ‘ Your AD Username/Password for SVN’hudson.util.IOException2: revision check failed on https://** at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:208) at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:138) at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:725) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:860) at hudson.scm.SCM.checkout(SCM.java:495) at hudson.model.AbstractProject.checkout(AbstractProject.java:1278) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1728) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404)Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled.svn: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled. at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:66) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:57) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:798) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:391) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:379) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:862) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:698) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:118) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1049) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:189) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:119) at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:195) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:46) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:160) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1235) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:968) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:873) at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:194) ... 12 moreCaused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled. at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:728) ...

[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

2017-02-03 Thread stefan.wal...@lisec.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Stefan Walter edited a comment on  JENKINS-32167  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ISVNAuthentication provider did not provide credentials   
 

  
 
 
 
 

 
 The issue still persists even with snapshot 2.7.2.{{No changes for https://** since the previous buildUsing sole credentials  in realm ‘ Your AD Username/Password for SVN’hudson.util.IOException2: revision check failed on https://** at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:208) at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:138) at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:725) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:860) at hudson.scm.SCM.checkout(SCM.java:495) at hudson.model.AbstractProject.checkout(AbstractProject.java:1278) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1728) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404)Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled.svn: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled. at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:66) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:57) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:798) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:391) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:379) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:862) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:698) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:118) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1049) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:189) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:119) at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:195) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:46) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:160) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1235) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:968) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:873) at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:194) ... 12 moreCaused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled. at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:728) ... 30

[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

2017-02-03 Thread stefan.wal...@lisec.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Stefan Walter commented on  JENKINS-32167  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ISVNAuthentication provider did not provide credentials   
 

  
 
 
 
 

 
 The issue still persists even with snapshot 2.7.2. {{No changes for https://** since the previous build Using sole credentials  in realm ‘ Your AD Username/Password for SVN’ hudson.util.IOException2: revision check failed on https://** at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:208) at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:138) at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:725) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:860) at hudson.scm.SCM.checkout(SCM.java:495) at hudson.model.AbstractProject.checkout(AbstractProject.java:1278) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1728) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404) Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled. svn: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled. at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:66) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:57) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:798) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:391) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:379) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:862) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:698) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:118) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1049) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:189) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:119) at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:195) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:46) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:160) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1235) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:968) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:873) at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:194) ... 12 more Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled. at

[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

2017-02-03 Thread jgl...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-32167  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ISVNAuthentication provider did not provide credentials   
 

  
 
 
 
 

 
 The snapshot is available here. Install using Plugin Manager » Advanced » Upload.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

2017-01-31 Thread stefan.wal...@lisec.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Stefan Walter commented on  JENKINS-32167  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ISVNAuthentication provider did not provide credentials   
 

  
 
 
 
 

 
 I would like to test this for you, because this is causing big issues for us. How can I install the snapshot?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

2017-01-31 Thread victor....@extronis.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Victor Ott updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-32167  
 
 
  ISVNAuthentication provider did not provide credentials   
 

  
 
 
 
 

 
Change By: 
 Victor Ott  
 
 
Environment: 
 Windows 7; Jenkins 1.617 with Subversion Plug-in 2.5.5Windows Server 2012 R2; Jenkins 2.19.3 with Subversion plugin 2.7.1 Linux x86_64, Jenkins 2.19.4 with Subversion Plugin 2.7.1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

2017-01-31 Thread dimitk...@java.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Dimitar Sakarov commented on  JENKINS-32167  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ISVNAuthentication provider did not provide credentials   
 

  
 
 
 
 

 
 The way we test it is really simple - every time when a location referenced as svn:external is updated, the next build/update fails.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick started work on  JENKINS-32167  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 Reopened In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick assigned an issue to Jesse Glick  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-32167  
 
 
  ISVNAuthentication provider did not provide credentials   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Assignee: 
 Manuel Recena Soto Jesse Glick  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-32167  
 
 
  ISVNAuthentication provider did not provide credentials   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Labels: 
 credentials diagnostics  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated  JENKINS-32167  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-32167  
 
 
  ISVNAuthentication provider did not provide credentials   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials