| "svn: authentication cancelled" error [message #557226] |
Mon, 06 September 2010 08:11  |
 Tomsen 
Messages: 42
Registered: July 2010 |
Member |
|
|
Hello,
I try to setup a build like here http:// wiki.eclipse.org/Building_an_RCP_application_with_hudson_%28 Buckminster%29 with separate jobs for Target Platform and actual product build.
The product build step is preceeded by an SVN checkout of the releng project.
A .cquery is then materialized in the workspace. The cquery also tries to fetch projects from the same SVN location. It seems now that the first SVN extract works, the second Buckminster driven extract does not with the error mentioned above.
Gestartet durch Benutzer anonymous
Checking out a fresh workspace because /home/hudson/jobs/xsl easy 4.0/workspace/de.softproject.xe.standalone.releng doesn't exist
Checking out https://svn-host/svn/MAIN/Products/Eclipse-RCP/XSLEasy/trunk/de.softproject.xe.standalone.releng
A build
A build/product.ant
A xsleasy36.rmap
A eclipse35dev.target
A buckminster_product.properties
A eclipse35.target
A .project
A buckminster.cspex
A buckminster_p2site.properties
A build-3.5.cquery
A build-3.6.cquery
A build.properties
A feature.xml
A xsleasy.target
A xsleasy35.rmap
At revision 29050
no change for https://svn-host/svn/MAIN/Products/Eclipse-RCP/XSLEasy/trunk/de.softproject.xe.standalone.releng since the previous build
[workspace] $ /usr/lib/jvm/java-6-sun/bin/java "-Dbuckminster.output.root=/home/hudson/jobs/xsl easy 4.0/workspace/buckminster.output" "-Dbuckminster.temp.root=/home/hudson/jobs/xsl easy 4.0/workspace/buckminster.temp" -Xmx256m -jar /home/hudson/tools/Buckminster_3.6/buckminster/plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar -application org.eclipse.buckminster.cmdline.headless -data "/home/hudson/jobs/xsl easy 4.0/workspace" --loglevel info -S "/home/hudson/jobs/xsl easy 4.0/workspace/commands.txt"
INFO: setpref 'targetPlatformPath=/home/hudson/jobs/xsl-easy Target Platform 3.5/builds/2010-09-06_09-02-37/archive//targetPlatform'
INFO: import '/home/hudson/jobs/xsl easy 4.0/workspace//de.softproject.xe.standalone.releng/build-3.6.cquery'
ERROR [0001] : No suitable provider for component de.softproject.xe.standalone.feature:eclipse.feature was found in resourceMap file:/home/hudson/jobs/xsl%20easy%204.0/workspace/de.softproject.xe.standalone.releng/xsleasy36.rmap
ERROR [0001] : No suitable provider for component de.softproject.xe.standalone.feature:eclipse.feature was found in searchPath de.softproject.xe
ERROR [0001] : Rejecting provider svn(https://{0}:{1}@{2}/svn/MAIN/Products/Eclipse-RCP/XSLEasy/trunk/{3}[https://xxx:yyy@svn-host/svn/MAIN/Products/Eclipse-RCP/XSLEasy/trunk/de.softproject.xe.standalone.feature]): No component match was found
ERROR org.tigris.subversion.svnclientadapter.SVNClientException: org.tigris.subversion.javahl.ClientException: svn: authentication cancelled
INFO: TAG-ID 0001 = Query for de.softproject.xe.standalone.feature:eclipse.feature
Archiviere Artefakte
Finished: FAILURE
Is this a known problem? I have found a post from last year with similar probloems. Is there a known workaround? I use the the 'auto'-setting for the Hudson SVN extract, maybe that conflicts with the Buckminster Plugin's Subclipse Default?
EDIT Just saw that the setting 'Repository Browser' probably is not the setting for the used SVN client but just for the browser used. Nevermind.
-Thomas
[Updated on: Mon, 06 September 2010 08:15] Report message to a moderator |
|
|
|
|
|
| Re: "svn: authentication cancelled" error [message #557277 is a reply to message #557264] |
Mon, 06 September 2010 12:19  |
Johannes Utzig
Messages: 329
Registered: July 2009 |
Senior Member |
|
|
Am 06.09.2010 13:08, schrieb Tomsen:
> Johannes,
> I had the wrong order of arguments in the import command. The properties
> are now accepted. SVN screws up still :( Weird that no-one else is
> seeing this problem. How do people normally get the cquery to populate
> the workspace? I would think you always check out the cquery from some
> repo and call "import" which in turn fetches more stuff from the same
> SVN. I could probably also just fetch everything from SVN first in
> pre-build so Buckminster does not have to go SVN .... but this seems
> like another hack.
> The setup works from the IDE btw.
>
> -Thomas
I think this has been fixed here:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=321733
But this revision is AFAIK not yet released. Meanwhile I you could
either switch to svn+ssh, or have the complete checkout done by hudson.
Having the checkout done by hudson is actually a very good alternative
if you for example check out a complete SVN module anyway. You get the
nice changelog per build, can configure hudson to build automatically on
changes in the SCM and so on.
Having Buckminster check out the source is preferable however if the
necessary bundles are spreaded through multiple SCMs, or modules in an
SCM and the number of artifacts to checkout is rather dynamic.
If you want to have the checkout done by hudson, I usually go with a
'hybrid rmap' that works for both developers and hudson:
<rm:searchPath name="yoursources">
<rm:provider componentTypes="osgi.bundle,eclipse.feature"
readerType="local">
<rm:uri format="file:///{0}/{1}/">
<bc:propertyRef key="workspace.root"/>
<bc:propertyRef key="buckminster.component"/>
</rm:uri>
</rm:provider>
<rm:provider
componentTypes="eclipse.feature,osgi.bundle,buckminster" readerType="cvs">
<rm:uri
format=":extssh:{0}@yourserver:22/var/share/cvs/,your/module{1} ">
<bc:propertyRef key="cvs.user"/>
<bc:propertyRef key="buckminster.component"/>
</rm:uri>
</rm:provider>
</rm:searchPath>
If the Build runs on Hudson, Hudson has already checked out everything,
so Buckminster will do a local resolution, expecting everything to be ar
workspace.root/component.name.
If a developer uses the same query, the 'local' provider fails so it
falls back the the cvs/svn/... provider and fetches the resources from
remote. That way you can easily use the same rmap for your headless
builds as well as for workspace provisioning for the developers.
Best regards,
Johannes
|
|
|
|
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03449 seconds
] 
Search
Help
Register
Login
Home
Apparently I can't use the syntax from the headless Buckminster commands. There 
Works like a charm. 
