Skip to main content

Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Buckminster » SVN update during materialization
SVN update during materialization [message #646901] Sun, 02 January 2011 20:56 Go to next message
Zoltan Ujhelyi is currently offline Zoltan UjhelyiFriend
Messages: 392
Registered: July 2015
Senior Member

thanks for the Buckminster tool, it is really useful for build automation.

I try to use Buckminster for continous integration together with Hudson, and selected Buckminster to download the required projects for the repository (in truth, we have a somewhat messy set of repositories, but the rmap allowed us to handle this with a simple set of rules - on the other hand manually specifying where to download what would be hard, and simply updating everything downloads a lot of code, and the rmap would be still hard to write...).

However, if the code in the repository changes, Buckminster does not update its workspace, but uses the previously checked-out projects. I found this old thread that suggest providing Advisor nodes in the cquery to prevent resolving from the workspace, and that would issue an update: 2.html Unluckily, this approach does not seem working for me.

My cquery looks like this:

<?xml version="1.0" encoding="UTF-8"?>
<cq:componentQuery xmlns:cq="" resourceMap=" nk/org.eclipse.viatra2.releng/viatra.rmap" properties=" nk/org.eclipse.viatra2.releng/">
<cq:rootRequest name="org.eclipse.viatra2.releng" componentType="eclipse.feature"/>
<cq:property key="target.arch" value="*"/>
<cq:property key="target.os" value="*"/>
<cq:property key="" value="*"/>
<cq:advisorNode namePattern="^hu\.optxware\.emf2viatra\.core" useMaterialization="false" useWorkspace="false"/>
<cq:advisorNode namePattern="^hu\.bme\.mit([\.\-].+)?" useMaterialization="false" useWorkspace="false"/>
<cq:advisorNode namePattern="^hu\.optxware\.emf2viatra\.core" useMaterialization="false" useWorkspace="false"/>

The referenced rmap uses the following locators:

<rm:locator pattern="^org\.eclipse\.viatra2([\.\-].+)?" searchPathRef="VIATRA_SVN" failOnError="false"/>
<rm:locator pattern="^hu\.bme\.mit([\.\-].+)?" searchPathRef="VIATRA_SVN"/>
<rm:locator pattern="^org\.eclipse\..*" searchPathRef=""/>
<rm:locator pattern="^hu\.optxware\.emf2viatra\.core" searchPathRef="VIATRA_SVN"/>
<rm:locator pattern="^com\.ibm([\.\-].+)" searchPathRef=""/>
<rm:locator pattern="^org\.apache([\.\-].+)" searchPathRef=""/>
<rm:locator pattern="^org\.sat4j([\.\-].+)" searchPathRef=""/>
<rm:locator pattern="^org\.junit([\.\-].+)" searchPathRef=""/>
<rm:locator pattern="^org\.junit" searchPathRef=""/>
<rm:locator pattern="^org\.hamcrest([\.\-].+)" searchPathRef=""/>

where points to the Helios update site, while VIATRA_SVN marks a set of repository URLs to check for the various projects. Name patterns are the same in both the locators and the cquery advisor nodes, and to projects get downloaded once.

Could you please help me to give a hint what have I done wrong, how to provide this functionality? I'm using the latest stable build of Buckminster (3.6.1) both in the IDE and in headless mode in the server.

Thank you in advance,
Zoltán Ujhelyi
Re: SVN update during materialization [message #647040 is a reply to message #646901] Tue, 04 January 2011 09:29 Go to previous messageGo to next message
Matthew Webber is currently offline Matthew WebberFriend
Messages: 198
Registered: December 2010
Senior Member
I haven't been able to get Buckminster to perform a Subversion update, either.

The only solution I can think of is to run the CQUERY to install any new dependencies that have been added since the previous run, and then do a separate svn update step on each component.
Re: SVN update during materialization [message #647051 is a reply to message #647040] Tue, 04 January 2011 11:00 Go to previous message
Zoltan Ujhelyi is currently offline Zoltan UjhelyiFriend
Messages: 392
Registered: July 2015
Senior Member
Thanks for the response.

I only asked because Thomas Hallgren wrote in the previously linked thread that its possible this way. Maybe I'm just missing a minor thing, but I have no idea left.

That manual SVN update seems doable using a simple shell script, but I would like to avoid a solution like that... Especially, because this means some kind of circle: buckminster install - svn update and the possible another round, because thanks to the refresh new plug-ins might be needed.
Previous Topic:Exceptions during import
Next Topic:list of internal properties?
Goto Forum:

Current Time: Tue Apr 16 17:30:05 GMT 2024

Powered by FUDForum. Page generated in 0.14061 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top