Sorry for the messages. But I see that in addition to the need for the
updated subversion plugin, something seems to have set the Credentials
in Jenkin's configuration to None. I selected the correct Credentials
(still in the popup menu for the setting). Now it gets further. It
checks out of some repos, but fails on a specific one that has the
same user/password. No idea why. The report that the failed repo is at
revision 0 is not correct. I suspect that it says so since it could
not access the repo. In the following, the first one works, but the
next one fails. In fact, 20 or so repos work ok before this failure.
Fetching 'http://sto-opq-src.scc.se/svn/Customers' at -1 into
'/home/jenkins/jobs/Nightly_Build/workspace/Customers'
At revision 147
Fetching 'http://sto-opq-src.scc.se/xsvn/PFU' at -1 into
'/home/jenkins/jobs/Nightly_Build/workspace/PFU'
At revision 0
ERROR: Failed to check out http://sto-opq-src.scc.se/svn/source.18.00
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.getNextAuthentication(DefaultSVNAuthenticationManager.java:215)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:685)
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.ng.SvnNgAbstractUpdate.handleExternalItemChange(SvnNgAbstractUpdate.java:347)
at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.handleExternalsChange(SvnNgAbstractUpdate.java:310)
at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.handleExternals(SvnNgAbstractUpdate.java:246)
at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.updateInternal(SvnNgAbstractUpdate.java:224)
at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.update(SvnNgAbstractUpdate.java:72)
at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgUpdate.run(SvnNgUpdate.java:38)
at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgUpdate.run(SvnNgUpdate.java:18)
at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgOperationRunner.run(SvnNgOperationRunner.java:20)
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.SVNUpdateClient.doUpdate(SVNUpdateClient.java:311)
at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:291)
at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:387)
at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:157)
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