Quantcast
Jenkins › Jenkins issues

[JIRA] (JENKINS-14168) scm-sync-configuration - Fails with E200015: authentication cancelled

classic Classic list List threaded Threaded
♦
♦
 16 messages Options
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-14168) scm-sync-configuration - Fails with E200015: authentication cancelled

JIRA noreply@jenkins-ci.org
Issue Type: Bug Bug
Affects Versions: current
Assignee: Frédéric Camblor
Components: scm-sync-configuration
Created: 20/Jun/12 8:40 PM
Description:

I was running Hudson 1.396 and using scm-sync-configuration without any problems.

I moved to Hudson 2.2.1 with a fresh install and configuration of Hudson. I have my jobs building correctly, but I cannot get scm-sync-configuration to work correctly. I even move the previous SVN folder into a tag and created an empty folder for it to populate, but I always get this error:

Unable to access http://beagle.hcs.us.com/svn/admin/trunk/ : svn: E200015: authentication cancelled

org.tmatesoft.svn.core.SVNCancelException: svn: E200015: authentication cancelled
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:37)
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:32)
at org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.getFirstAuthentication(DefaultSVNAuthenticationManager.java:177)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:580)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:286)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:274)
at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:696)
at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:619)
at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:103)
at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1016)
at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.testConnection(DAVRepository.java:99)
at hudson.scm.SubversionSCM$DescriptorImpl.checkRepositoryPath(SubversionSCM.java:2014)
at hudson.scm.SubversionSCM$DescriptorImpl.doCheckRemote(SubversionSCM.java:1945)
at sun.reflect.GeneratedMethodAccessor182.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:282)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:149)
at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:88)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:103)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:233)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:233)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:489)
at org.kohsuke.stapler.Stapler.service(Stapler.java:160)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
at winstone.ServletConfiguration.execute(ServletConfiguration.java:249)
at winstone.RequestDispatcher.forward(RequestDispatcher.java:335)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:378)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:94)
at org.hudsonci.servlets.internal.ServletRegistrationFilterAdapter.doFilter(ServletRegistrationFilterAdapter.java:180)
at org.hudsonci.servlets.internal.ServletRegistrationFilterAdapter.doFilter(ServletRegistrationFilterAdapter.java:148)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:97)
at org.hudsonci.servlets.internal.ServletRegistrationFilterAdapter.doFilter(ServletRegistrationFilterAdapter.java:180)
at org.hudsonci.servlets.internal.ServletRegistrationFilterAdapter.doFilter(ServletRegistrationFilterAdapter.java:148)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:97)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:86)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:195)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:368)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:195)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:368)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:195)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:368)
at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:195)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:368)
at winstone.RequestDispatcher.forward(RequestDispatcher.java:333)
at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:244)
at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150)
at java.lang.Thread.run(Unknown Source)

(Maybe you need to enter credential?)

----- End Copy and Paste —
Entering a credential doesn't work, even if I mark it as global override. I created a Hudson job (as requested in the troubleshooting) and it is able to checkout the folder without problems.

I also followed the instructions here:
http://blog.vinodsingh.com/2009/08/hudson-svn-authentication-cancelled.html
However, I'm on Windows, so I may have missed something I should have deleted (I deleted the folder under Application Data and it didn't come back).

At this point, I'm at a loss as to how to make it work.

Thanks for your help.
Environment: Windows
Hudson 2.2.1
Project: Jenkins
Labels: plugin subversion exception
Priority: Major Major
Reporter: Stephen M
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-14168) scm-sync-configuration - Fails with E200015: authentication cancelled

JIRA noreply@jenkins-ci.org
Stephen M commented on Bug JENKINS-14168

From the log file:

SCM Sync Logger

Jun 20, 2012 3:27:40 PM hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiated
WARNING: SCM Repository has not yet been initiated !

Jun 20, 2012 3:27:34 PM hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiated
WARNING: SCM Repository has not yet been initiated !

Jun 20, 2012 3:27:16 PM hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiated
WARNING: SCM Repository has not yet been initiated !

Jun 20, 2012 3:26:27 PM hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiated
WARNING: SCM Repository has not yet been initiated !

Jun 20, 2012 3:26:16 PM hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiated
WARNING: SCM Repository has not yet been initiated !

Jun 20, 2012 3:25:38 PM hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiated
WARNING: SCM Repository has not yet been initiated !

Jun 20, 2012 3:25:32 PM hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiated
WARNING: SCM Repository has not yet been initiated !

Jun 20, 2012 3:25:13 PM hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiated
WARNING: SCM Repository has not yet been initiated !

Jun 20, 2012 3:24:27 PM hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiated
WARNING: SCM Repository has not yet been initiated !

Jun 20, 2012 3:24:26 PM hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiated
WARNING: SCM Repository has not yet been initiated !

Jun 20, 2012 2:45:18 PM hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiated
WARNING: SCM Repository has not yet been initiated !

Jun 20, 2012 2:45:06 PM hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiated
WARNING: SCM Repository has not yet been initiated !

Jun 20, 2012 2:45:06 PM hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiated
WARNING: SCM Repository has not yet been initiated !

Jun 20, 2012 2:45:06 PM hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiated
WARNING: SCM Repository has not yet been initiated !

Jun 20, 2012 2:45:06 PM hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiated
WARNING: SCM Repository has not yet been initiated !

Jun 20, 2012 2:45:06 PM hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiated
WARNING: SCM Repository has not yet been initiated !

Jun 20, 2012 2:45:06 PM hudson.plugins.scm_sync_configuration.scms.impl.ScmSyncSubversionSCM extractScmCredentials
SEVERE: No credentials are stored in Hudson for realm <<http://beagle.hcs.us.com:80> Subversion repository> !

Jun 20, 2012 2:45:06 PM hudson.plugins.scm_sync_configuration.scms.impl.ScmSyncSubversionSCM extractScmCredentials
INFO: Extracting SVN Credentials for url : http://beagle.hcs.us.com/svn/admin/trunk/

Jun 20, 2012 2:45:06 PM hudson.plugins.scm_sync_configuration.SCMManipulator scmConfigurationSettledUp
INFO: Creating scmRepository connection data ..

Jun 20, 2012 2:44:55 PM hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiated
WARNING: SCM Repository has not yet been initiated !

Jun 20, 2012 2:44:44 PM hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiated
WARNING: SCM Repository has not yet been initiated !

Jun 20, 2012 2:44:44 PM hudson.plugins.scm_sync_configuration.scms.impl.ScmSyncSubversionSCM extractScmCredentials
SEVERE: No credentials are stored in Hudson for realm <<http://beagle.hcs.us.com:80> Subversion repository> !

Jun 20, 2012 2:44:44 PM hudson.plugins.scm_sync_configuration.scms.impl.ScmSyncSubversionSCM extractScmCredentials
INFO: Extracting SVN Credentials for url : http://beagle.hcs.us.com/svn/admin/trunk/hudson/

Jun 20, 2012 2:44:44 PM hudson.plugins.scm_sync_configuration.SCMManipulator scmConfigurationSettledUp
INFO: Creating scmRepository connection data ..
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-14168) scm-sync-configuration - Fails with E200015: authentication cancelled

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

Hi Stephen,

In your HUDSON_HOME/hudson.scm.SubversionSCM.xml, do you have a <credentials> tag with entries inside it ?

If this is the case, do you have an entry with exact key "<http://beagle.hcs.us.com:80> Subversion repository" ?
Something like this :
<hudson.scm.SubversionSCM_-DescriptorImpl>
<helpRedirect/>
<generation>32</generation>
<credentials class="hashtable">
<entry>
<string><<a href="http://beagle.hcs.us.com:80&amp;gt">http://beagle.hcs.us.com:80&gt; Subversion repository</string>
<hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
<userName>XXXXX</userName>
<password>XXXXX</password>
</hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
</entry>
</credentials>
<workspaceFormat>8</workspaceFormat>
<validateRemoteUpToVar>false</validateRemoteUpToVar>
<storeAuthToDisk>true</storeAuthToDisk>
</hudson.scm.SubversionSCM_-DescriptorImpl>

If you already have credential entries, which doesn't exactly match expected key, try to clone it and change the key to the expected one (keeping the encrypted password).
If you don't have any credential entries, I think you're not storing correctly your hudson credentials (re-read the troubleshoot page)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-14168) scm-sync-configuration - Fails with E200015: authentication cancelled

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
 
Frédéric Camblor edited a comment on Bug JENKINS-14168

Hi Stephen,

In your HUDSON_HOME/hudson.scm.SubversionSCM.xml, do you have a <credentials> tag with entries inside it ?

If this is the case, do you have an entry with exact key "<http://beagle.hcs.us.com:80> Subversion repository" ?
Something like this :
<hudson.scm.SubversionSCM_-DescriptorImpl>
<helpRedirect/>
<generation>32</generation>
<credentials class="hashtable">
<entry>
<string>&lt;<a href="http://beagle.hcs.us.com:80&amp;gt">http://beagle.hcs.us.com:80&gt; Subversion repository</string>
<hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
<userName>XXXXX</userName>
<password>XXXXX</password>
</hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
</entry>
</credentials>
<workspaceFormat>8</workspaceFormat>
<validateRemoteUpToVar>false</validateRemoteUpToVar>
<storeAuthToDisk>true</storeAuthToDisk>
</hudson.scm.SubversionSCM_-DescriptorImpl>

If you already have credential entries, which doesn't exactly match expected key, try to clone it and change the key to the expected one (keeping the encrypted password).
If you don't have any credential entries, I think you're not storing correctly your hudson credentials (re-read the troubleshoot page)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-14168) scm-sync-configuration - Fails with E200015: authentication cancelled

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
 
Frédéric Camblor edited a comment on Bug JENKINS-14168

Hi Stephen,

In your HUDSON_HOME/hudson.scm.SubversionSCM.xml, do you have a <credentials> tag with entries inside it ?

If this is the case, do you have an entry with exact key "<http://beagle.hcs.us.com:80> Subversion repository" ?
Something like this :
<hudson.scm.SubversionSCM_-DescriptorImpl>
<helpRedirect/>
<generation>32</generation>
<credentials class="hashtable">
<entry>
<string>&lt;<a href="http://beagle.hcs.us.com:80&amp;gt">http://beagle.hcs.us.com:80&gt; Subversion repository</string>
<hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
<userName>XXXXX</userName>
<password>XXXXX</password>
</hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
</entry>
</credentials>
<workspaceFormat>8</workspaceFormat>
<validateRemoteUpToVar>false</validateRemoteUpToVar>
<storeAuthToDisk>true</storeAuthToDisk>
</hudson.scm.SubversionSCM_-DescriptorImpl>

If you already have credential entries, which doesn't exactly match expected key, try to clone it and change the key to the expected one (keeping the encrypted password, and escaping < and > tags with &lt; and >).
If you don't have any credential entries, I think you're not storing correctly your hudson credentials (re-read the troubleshoot page)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-14168) scm-sync-configuration - Fails with E200015: authentication cancelled

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
 
Frédéric Camblor edited a comment on Bug JENKINS-14168

Hi Stephen,

In your HUDSON_HOME/hudson.scm.SubversionSCM.xml, do you have a <credentials> tag with entries inside it ?

If this is the case, do you have an entry with exact key "<http://beagle.hcs.us.com:80> Subversion repository" ?
Something like this :
<hudson.scm.SubversionSCM_-DescriptorImpl>
<helpRedirect/>
<generation>32</generation>
<credentials class="hashtable">
<entry>
<string>&lt;<a href="http://beagle.hcs.us.com:80&amp;gt">http://beagle.hcs.us.com:80&gt; Subversion repository</string>
<hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
<userName>XXXXX</userName>
<password>XXXXX</password>
</hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
</entry>
</credentials>
<workspaceFormat>8</workspaceFormat>
<validateRemoteUpToVar>false</validateRemoteUpToVar>
<storeAuthToDisk>true</storeAuthToDisk>
</hudson.scm.SubversionSCM_-DescriptorImpl>

If you already have credential entries, which doesn't exactly match expected key, try to clone it and change the key to the expected one (keeping the encrypted password, and escaping < and > tags with &lt; and &gt.
If you don't have any credential entries, I think you're not storing correctly your hudson credentials (re-read the troubleshoot page)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-14168) scm-sync-configuration - Fails with E200015: authentication cancelled

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
 
Frédéric Camblor edited a comment on Bug JENKINS-14168

Hi Stephen,

In your HUDSON_HOME/hudson.scm.SubversionSCM.xml, do you have a <credentials> tag with entries inside it ?

If this is the case, do you have an entry with exact key "<http://beagle.hcs.us.com:80> Subversion repository" ?
Something like this :
<hudson.scm.SubversionSCM_-DescriptorImpl>
<helpRedirect/>
<generation>32</generation>
<credentials class="hashtable">
<entry>
<string>&lt;<a href="http://beagle.hcs.us.com:80&amp;gt">http://beagle.hcs.us.com:80&gt; Subversion repository</string>
<hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
<userName>XXXXX</userName>
<password>XXXXX</password>
</hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
</entry>
</credentials>
<workspaceFormat>8</workspaceFormat>
<validateRemoteUpToVar>false</validateRemoteUpToVar>
<storeAuthToDisk>true</storeAuthToDisk>
</hudson.scm.SubversionSCM_-DescriptorImpl>

If you already have credential entries, which doesn't exactly match expected key, try to clone it and change the key to the expected one (keeping the encrypted password, and escaping < and > tags with &lt; and &gt; ).
If you don't have any credential entries, I think you're not storing correctly your hudson credentials (re-read the troubleshoot page)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-14168) scm-sync-configuration - Fails with E200015: authentication cancelled

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
Stephen M commented on Bug JENKINS-14168

Hi Frederic,
Thank you for your reply.

Looks like an exact match to me. Here is my hudson.scm.SubversionSCM.xml (with password and username removed):

<?xml version='1.0' encoding='UTF-8'?>
<hudson.scm.SubversionSCM_-DescriptorImpl>
<generation>8</generation>
<credentials class="hashtable">
<entry>
<string><<a href="http://beagle.hcs.us.com:80&amp;gt">http://beagle.hcs.us.com:80&gt;</string>
<hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
<userName>XXXXX</userName>
<password>XXXXX</password>
</hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
</entry>
</credentials>
<workspaceFormat>10</workspaceFormat>
<revisionPolicy>QUEUE_TIME</revisionPolicy>
<validateRemoteUpToVar>false</validateRemoteUpToVar>
</hudson.scm.SubversionSCM_-DescriptorImpl>

Could it be a problem that our Jobs and SCM Sync need the same username and password? Okay, I'm grasping at straws here.

Thanks again for your help!
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-14168) scm-sync-configuration - Fails with E200015: authentication cancelled

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
Stephen M commented on Bug JENKINS-14168

The less than before the URL is correct, but this forum is rendering it instead of leaving it as the four characters & l t ;.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-14168) scm-sync-configuration - Fails with E200015: authentication cancelled

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
 
Stephen M edited a comment on Bug JENKINS-14168

The less than before the URL is correct, but this forum is rendering it instead of leaving it as the four characters & l t ;.
Now fixed above with a formatting trick.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-14168) scm-sync-configuration - Fails with E200015: authentication cancelled

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
 
Stephen M edited a comment on Bug JENKINS-14168

Hi Frederic,
Thank you for your reply.

Looks like an exact match to me. Here is my hudson.scm.SubversionSCM.xml (with password and username removed):

<?xml version='1.0' encoding='UTF-8'?>
<hudson.scm.SubversionSCM_-DescriptorImpl>
  <generation>8</generation>
  <credentials class="hashtable">
    <entry>
      <string>&lt;http://beagle.hcs.us.com:80&gt;</string>
      <hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
        <userName>XXXXX</userName>
        <password>XXXXX</password>
      </hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
    </entry>
  </credentials>
  <workspaceFormat>10</workspaceFormat>
  <revisionPolicy>QUEUE_TIME</revisionPolicy>
  <validateRemoteUpToVar>false</validateRemoteUpToVar>
</hudson.scm.SubversionSCM_-DescriptorImpl>

Could it be a problem that our Jobs and SCM Sync need the same username and password? Okay, I'm grasping at straws here.

Thanks again for your help!
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-14168) scm-sync-configuration - Fails with E200015: authentication cancelled

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
 
Stephen M edited a comment on Bug JENKINS-14168

Hi Frederic,
Thank you for your reply.

Looks like an exact match to me. Here is my hudson.scm.SubversionSCM.xml (with password and username removed):

<?xml version='1.0' encoding='UTF-8'?>
<hudson.scm.SubversionSCM_-DescriptorImpl>
  <generation>8</generation>
  <credentials class="hashtable">
    <entry>
      <string>&lt;http://beagle.hcs.us.com:80&gt;</string>
      <hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
        <userName>XXXXX</userName>
        <password>XXXXX</password>
      </hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
    </entry>
  </credentials>
  <workspaceFormat>10</workspaceFormat>
  <revisionPolicy>QUEUE_TIME</revisionPolicy>
  <validateRemoteUpToVar>false</validateRemoteUpToVar>
</hudson.scm.SubversionSCM_-DescriptorImpl>

Could it be a problem that our Jobs and SCM Sync need the same username and password?  Okay, I'm grasping at straws here.

Thanks again for your help!
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-14168) scm-sync-configuration - Fails with E200015: authentication cancelled

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
Stephen M commented on Bug JENKINS-14168

I missed the "Subversion respository" on the end. Changed my file to read:

<?xml version='1.0' encoding='UTF-8'?>
<hudson.scm.SubversionSCM_-DescriptorImpl>
  <generation>8</generation>
  <credentials class="hashtable">
    <entry>
      <string>&lt;http://beagle.hcs.us.com:80&gt;</string>
      <hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
        <userName>XXXXX</userName>
        <password>XXXXX</password>
      </hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
    </entry>
    <entry>
      <string>&lt;http://beagle.hcs.us.com:80&gt; Subversion repository</string>
      <hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
        <userName>XXXXX</userName>
        <password>XXXXX</password>
      </hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
    </entry>
  </credentials>
  <workspaceFormat>10</workspaceFormat>
  <revisionPolicy>QUEUE_TIME</revisionPolicy>
  <validateRemoteUpToVar>false</validateRemoteUpToVar>
</hudson.scm.SubversionSCM_-DescriptorImpl>

However, even after a Hudson reload of the configuration files, I'm still seeing the same exception and the same warnings in the log file.

Jun 20, 2012 5:06:45 PM hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiated
WARNING: SCM Repository has not yet been initiated !

Jun 20, 2012 5:05:58 PM hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiated
WARNING: SCM Repository has not yet been initiated !

Jun 20, 2012 5:03:34 PM hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiated
WARNING: SCM Repository has not yet been initiated !

Any ideas?

Thanks again!
--Stephen
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-14168) scm-sync-configuration - Fails with E200015: authentication cancelled

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

Do you still have following errors ?

Jun 20, 2012 2:45:06 PM hudson.plugins.scm_sync_configuration.scms.impl.ScmSyncSubversionSCM extractScmCredentials
SEVERE: No credentials are stored in Hudson for realm <<http://beagle.hcs.us.com:80> Subversion repository> !

It was this line which bugged me yesterday

Just in case, could you clone your credential entry and remove the ":80" inside your scm host url ? (won't bet on this but heh... who knows ... )
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-14168) scm-sync-configuration - Fails with E200015: authentication cancelled

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
Stephen M commented on Bug JENKINS-14168

Okay, it fixed itself without any further changes on my part. Weird. It seemed to need a restart of Hudson, but I'm pretty such I'd done that before.

Marking as resolved.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-14168) scm-sync-configuration - Fails with E200015: authentication cancelled

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
Stephen M resolved Bug JENKINS-14168 as Cannot Reproduce

Problem went away on its own.

Thanks for your help!
Change By: Stephen M (25/Jun/12 2:49 PM)
Status: Open Resolved
Resolution: Cannot Reproduce
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Loading...
Powered by Nabble Edit this page