[JIRA] (JENKINS-25070) Subversion fails to update externals once after external is changed.
Title: Message Title Ivan Fernandez Calvo closed an issue as Duplicate Jenkins / JENKINS-25070 Subversion fails to update externals once after external is changed. Change By: Ivan Fernandez Calvo Status: Open Closed Resolution: Duplicate 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-25070) Subversion fails to update externals once after external is changed.
Title: Message Title Sebastian Götz commented on JENKINS-25070 Re: Subversion fails to update externals once after external is changed. After reading the comments in JENKINS-31455 I think it has the same origin, but seems to be another problem. Our builds fail each time, a source uses as an external is being change (which happens not very often in our projects). After that I have to run the same build again and it works until the next change to an external. Sometimes after restarting Jenkins it also happens, But this not as predictable as the case of a changed svn:external. 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-25070) Subversion fails to update externals once after external is changed.
Title: Message Title Joachim Herb commented on JENKINS-25070 Re: Subversion fails to update externals once after external is changed. Is this the same bug as https://issues.jenkins-ci.org/browse/JENKINS-31455 ? 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-25070) Subversion fails to update externals once after external is changed.
Title: Message Title Markus Franke commented on JENKINS-25070 Re: Subversion fails to update externals once after external is changed. Hmmsorry for that. But I did not have any URI scheme filter set and it also fails. However, I am still getting Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: authentication cancelled 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-25070) Subversion fails to update externals once after external is changed.
Title: Message Title
Markus Franke edited a comment on JENKINS-25070
Re: Subversion fails to update externals once after external is changed.
Hmmsorry for that. But I did not have any URI scheme filter set and it also fails. However, I am still getting{{Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: authentication cancelled}}
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-25070) Subversion fails to update externals once after external is changed.
Title: Message Title
Sebastian Götz edited a comment on JENKINS-25070
Re: Subversion fails to update externals once after external is changed.
When configuring the credentials of a domain you have the possibility to add/remove filters to specify when these credentials apply ({{hostname, hostname:port, URI scheme, URI path}}). With my specification I used the {{hostname}} and the {{URI scheme}} filter. To fix the issue I simple removed the {{URI scheme}} stuff and stored the configuration. Until now it works for me. +EDIT:+Unortunately just this morning the nightly build failed with the same exception then ever:{{svn: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled.}}
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-25070) Subversion fails to update externals once after external is changed.
Title: Message Title Sebastian Götz commented on JENKINS-25070 Re: Subversion fails to update externals once after external is changed. When configuring the credentials of a domain you have the possibility to add/remove filters to specify when these credentials apply (hostname, hostname:port, URI scheme, URI path). With my specification I used the hostname and the URI scheme filter. To fix the issue I simple removed the URI scheme stuff and stored the configuration. Until now it works for me. 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-25070) Subversion fails to update externals once after external is changed.
Title: Message Title Markus Franke commented on JENKINS-25070 Re: Subversion fails to update externals once after external is changed. What do you mean by "removed the URI scheme filter"? I still have problems to get this working. 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-25070) Subversion fails to update externals once after external is changed.
Title: Message Title Sebastian Götz commented on JENKINS-25070 Re: Subversion fails to update externals once after external is changed. Looks like this does the trick in deed. I simple removed the URI scheme filter from the domain description and saved the stuff again, although the theme was correct. Seems like now its working. 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-25070) Subversion fails to update externals once after external is changed.
Title: Message Title Sebastian Götz edited a comment on JENKINS-25070 Re: Subversion fails to update externals once after external is changed. Looks like this does the trick in deed. I simple removed the URI scheme filter from the domain description and saved the stuff again, although the theme was correct. Seems like now its it's working.:P 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-25070) Subversion fails to update externals once after external is changed.
Title: Message Title Mengesteab Ghebreyesus commented on JENKINS-25070 Re: Subversion fails to update externals once after external is changed. You enter the Realm and the same Credentials again. The credential got lost, who knows what the reasen is. 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-25070) Subversion fails to update externals once after external is changed.
Title: Message Title Sebastian Götz commented on JENKINS-25070 Re: Subversion fails to update externals once after external is changed. How did you suply these additional credentials? The "externals" we have are actually in the same repository (same server, same repo). 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-25070) Subversion fails to update externals once after external is changed.
Title: Message Title Mengesteab Ghebreyesus commented on JENKINS-25070 Re: Subversion fails to update externals once after external is changed. Additional Credentials fixed our problem. 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-25070) Subversion fails to update externals once after external is changed.
Title: Message Title Sebastian Götz commented on JENKINS-25070 Re: Subversion fails to update externals once after external is changed. Hi guys, we are facing a similar problem. We have subdirectory within the same subversion repository the code resides in for common files like certificates an so on. Each time such an svn:external changes the following build fails with the message: hudson.util.IOException2: revision check failed on at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:207) at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:137) at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:722) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:857) at hudson.scm.SCM.checkout(SCM.java:485) at hudson.model.AbstractProject.checkout(AbstractProject.java:1269) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:607) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1738) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) 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: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:793) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:398) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:386) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:863) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:699) 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: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.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
