I have looked a bit more and I see there is a bit more information:
Unable to access http://sto-opq-src.scc.se/svn/source.18.00 : svn:
E200015: E200015: ISVNAuthentication provider did not provide
credentials; HTTP authorization cancelled.
svn: E200015: ISVNAuthentication provider did not provide credentials;
HTTP authorization cancelled.
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.testConnection(DAVRepository.java:94)
at hudson.scm.SubversionSCM$DescriptorImpl.checkRepositoryPath(SubversionSCM.java:2282)
at hudson.scm.SubversionSCM$ModuleLocation$DescriptorImpl.checkCredentialsId(SubversionSCM.java:3043)
at hudson.scm.SubversionSCM$ModuleLocation$DescriptorImpl.doCheckCredentialsId(SubversionSCM.java:3016)
I can do subversion updates as the Jenkins user ok. So the basic
access to the subversion server is still okay. The problem seems to be
when Jenkins is doing the subversion update on it's own.
On Wed, Jan 7, 2015 at 1:47 PM, Roger Oberholtzer
Indeed there were a few plugin updates available. I saw that there was one for subversion. I updated it and restarted both Jenkins and Apache. Now I get the following:
Building in workspace /home/jenkins/jobs/Nightly_Build/workspace Updating http://sto-opq-src.scc.se/svn/source.18.00 at revision '2015-01-07T13:43:54.620 +0100' ERROR: Subversion update has been canceled Build was aborted Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered Finished: ABORTED
On Wed, Jan 7, 2015 at 1:34 PM, Aaron Digulla
wrote: Am Mittwoch, 07. Januar 2015 07:44 CET, Roger Oberholtzer
schrieb: No one using Jenkins? A search in the openSUSE forum for jenkins returns nothing at all related to the program. How odd. I cannot believe I am the only one with this issue.
Does anyone know which version of Java Jenkins likes on openSUSE? I did not change the Java implementation, but it was also updated when
Jenkins was updated.
The error message indicates that access to a native library is broken: The tmatesoft SVN plugin of Jenkins tries to access the GNOME keyring.
FATAL: com.sun.jna.Structure.getFieldOrder()Ljava/util/List; java.lang.AbstractMethodError: com.sun.jna.Structure.getFieldOrder()Ljava/util/List; at com.sun.jna.Structure.fieldOrder(Structure.java:884) [...] at org.tmatesoft.svn.core.internal.util.jna.SVNGnomeKeyring$GnomeKeyringContext.<init>(SVNGnomeKeyring.java:324)
Check those libraries for updates.
Regards,
-- Aaron "Optimizer" Digulla a.k.a. Philmann Dark "It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits." http://blog.pdark.de/
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- Roger Oberholtzer
-- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org