Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-29340

E200015: ISVNAuthentication provider did not provide credentials

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • subversion-plugin
    • * Jenkins version 1.613
      * Subversion Plugin version 2.5.1
      * Env Inject Plugin version 1.91.3

    Description

      Steps to reproduce the bug

      • Configure Job enabling Prepare environment for the run
      • Create a variable REPOSITORIO
      • Define svn url using created variable REPOSITORIO
      • Add credentials
      • Configure check scm every minute (testing purposes)

      Error

      scmPollLog error:

      Started on 10-jul-2015 11:19:00
      Received SCM poll call on master for OXM_IC on 10-jul-2015 11:19:00
      ERROR: Error al obtener la revisión http://subversion-dsa.gva.es/svn/oxm/trunk del repositorio
      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:60)
      	at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
      	at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:759)
      	at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:371)
      	at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:359)
      	at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:710)
      	at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627)
      	at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102)
      	at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1032)
      	at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:175)
      	at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118)
      	at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:184)
      	at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45)
      	at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteGetInfo.run(SvnRemoteGetInfo.java:46)
      	at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteGetInfo.run(SvnRemoteGetInfo.java:31)
      	at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21)
      	at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1259)
      	at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294)
      	at org.tmatesoft.svn.core.wc.SVNWCClient.doInfo(SVNWCClient.java:2523)
      	at hudson.scm.SubversionSCM.parseSvnInfo(SubversionSCM.java:1223)
      	at hudson.scm.CompareAgainstBaselineCallable.call(CompareAgainstBaselineCallable.java:78)
      	at hudson.scm.CompareAgainstBaselineCallable.call(CompareAgainstBaselineCallable.java:26)
      	at hudson.remoting.LocalChannel.call(LocalChannel.java:45)
      	at hudson.scm.SubversionSCM.compareRemoteRevisionWith(SubversionSCM.java:1408)
      	at hudson.scm.SCM.compareRemoteRevisionWith(SCM.java:381)
      	at hudson.scm.SCM.poll(SCM.java:398)
      	at hudson.model.AbstractProject._poll(AbstractProject.java:1453)
      	at hudson.model.AbstractProject.poll(AbstractProject.java:1356)
      	at jenkins.triggers.SCMTriggerItem$SCMTriggerItems$Bridge.poll(SCMTriggerItem.java:119)
      	at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:510)
      	at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:539)
      	at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118)
      	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
      	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
      	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
      	at java.lang.Thread.run(Thread.java:745)
      Caused 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:689)
      	... 34 more
      Done. Took 0,13 Seg
      No changes
      

      Attachments

        Issue Links

          Activity

            ralf_muehle

            Please, file a new JIRA ticket including a step by step process to reproduce the bug.

            The bug described in this ticket was resolved and confirmed by users.

            recena Manuel Recena Soto added a comment - ralf_muehle Please, file a new JIRA ticket including a step by step process to reproduce the bug. The bug described in this ticket was resolved and confirmed by users.
            ralf_muehle Ralf Mühle added a comment - - edited

            After JENKINS-29352 is marked as duplicate of this bug:
            With Jenkins 1.629 and SVN Plugin 2.5.3 the bug is not resolved.

            Location 'https://xxxx/${SVN_TRUNK}' does not exist
            One or more repository locations do not exist anymore for hudson.maven.MavenModuleSet@a8864af[TEST_MVN_JOB], project will be disabled.
            The project has been disabled

            SVN_TRUNK is a global environment variable defined in Mange Jenkins - Configure System - Global Properties - Env. Variables

            I get this error with a maven project and freestyle project

            ralf_muehle Ralf Mühle added a comment - - edited After JENKINS-29352 is marked as duplicate of this bug: With Jenkins 1.629 and SVN Plugin 2.5.3 the bug is not resolved. Location 'https://xxxx/${SVN_TRUNK}' does not exist One or more repository locations do not exist anymore for hudson.maven.MavenModuleSet@a8864af[TEST_MVN_JOB], project will be disabled. The project has been disabled SVN_TRUNK is a global environment variable defined in Mange Jenkins - Configure System - Global Properties - Env. Variables I get this error with a maven project and freestyle project

            esheffield, I think it is better if you use jenkinsci-user mailing list to share your request. In my opinion, EnvInject is not designed for that.

            recena Manuel Recena Soto added a comment - esheffield , I think it is better if you use jenkinsci-user mailing list to share your request. In my opinion, EnvInject is not designed for that.

            recena Ah, apologies, I didn't notice this caveat. Thank you for pointing that out. Do you know if there are any workarounds that would allow me to load that environment variable dynamically? The value I'm depending on is generated by running another job, so it doesn't seem like I would be able to load it using "Properties Content".

            esheffield Evan Sheffield added a comment - recena Ah, apologies, I didn't notice this caveat. Thank you for pointing that out. Do you know if there are any workarounds that would allow me to load that environment variable dynamically? The value I'm depending on is generated by running another job, so it doesn't seem like I would be able to load it using "Properties Content".

            esheffield, Please, read the help information.

            Properties Content

            These environment variables (only these) will be available in the Job environment independently from the build. There are following use-cases: SCM polling, validation of fields depending on environment variables (e.g. http://server/svn/$REPO), custom workspace management, etc.

            recena Manuel Recena Soto added a comment - esheffield , Please, read the help information . Properties Content These environment variables ( only these ) will be available in the Job environment independently from the build. There are following use-cases: SCM polling, validation of fields depending on environment variables (e.g. http://server/svn/$REPO ), custom workspace management, etc.

            People

              recena Manuel Recena Soto
              ricardogarfe Ricardo García Fernández
              Votes:
              1 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: