Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Buckminster » General approaches for providing materializations
General approaches for providing materializations [message #546694] Tue, 13 July 2010 15:21 Go to next message
Miles Parker is currently offline Miles Parker
Messages: 1338
Registered: July 2009
Senior Member
Hi,

I'm wondering what people are doing for providing the easiest possible paths to users for workspace setup. I have two issues I'm thinking about right now. My goal is to have a sort of team project set on steroids. (Actually, that's a bad example because steroids are not sustainable in long term!)

1. Is it possible to provide a single artifact to users? Right now I'm down to a cspec and rmap but it would be ideal for them to be able to simply go to a single URL. Although, I guess I could simply fully specify a URL for the rmap.

2. Is there a way to handle SVN / CVS credentials if cooresponding repos haven't already been created? the only way it works for me now is with the repos, which means asking the users to put in the svn, which is really half the battle.

I see big advantages to this to using a .psf file, not least is that generally speaking they should never go out of date.
Re: General approaches for providing materializations [message #546712 is a reply to message #546694] Tue, 13 July 2010 17:42 Go to previous messageGo to next message
Miles Parker is currently offline Miles Parker
Messages: 1338
Registered: July 2009
Senior Member
I can answer my own question now..

It seems that all you have to ask your users to do is provide a URL to the cspec in the form with the password and user name, i.e. https://myname:mypw@myserver.foo.com/myproject/releng/myproj ect.site/site.cspec

and Buckminster takes care of the rest. Neat..

Re: General approaches for providing materializations [message #546735 is a reply to message #546712] Tue, 13 July 2010 22:17 Go to previous messageGo to next message
Henrik Lindberg is currently offline Henrik Lindberg
Messages: 2499
Registered: July 2009
Senior Member
Did you perhaps mean xxx.cquery?

The typical setup is to have different cqueries (or mspecs if required
for non standard TP processing) for different purposes - different
development streams if you like - and developers just pick the one they
should use, using some obvious naming ("latest", "3-2-maintenance", etc.)

- henrik


On 7/13/10 11:42 PM, Miles Parker wrote:
> I can answer my own question now..
>
> It seems that all you have to ask your users to do is provide a URL to
> the cspec in the form with the password and user name, i.e.
> https://myname:mypw@myserver.foo.com/myproject/releng/myproj ect.site/site.cspec
>
>
> and Buckminster takes care of the rest. Neat..
>
>
Re: General approaches for providing materializations [message #546736 is a reply to message #546735] Tue, 13 July 2010 22:31 Go to previous messageGo to next message
Miles Parker is currently offline Miles Parker
Messages: 1338
Registered: July 2009
Senior Member
Henrik Lindberg wrote on Tue, 13 July 2010 22:17
Did you perhaps mean xxx.cquery?


Yes, that's exactly what I *meant*..

Quote:
The typical setup is to have different cqueries (or mspecs if required
for non standard TP processing) for different purposes - different
development streams if you like - and developers just pick the one they
should use, using some obvious naming ("latest", "3-2-maintenance", etc.)


Yep, that makes a lot of sense. For me it's more a matter of giving people a smooth reproducable path to just the pieces that they want to work with. I'm thinking now that the pain of last week or so is worth it. Thanks!
Re: General approaches for providing materializations [message #546773 is a reply to message #546694] Wed, 14 July 2010 03:32 Go to previous message
Johannes Utzig is currently offline Johannes Utzig
Messages: 329
Registered: July 2009
Senior Member
Am 13.07.2010 21:21, schrieb Miles Parker:
> 1. Is it possible to provide a single artifact to users? Right now I'm
> down to a cspec and rmap but it would be ideal for them to be able to
> simply go to a single URL. Although, I guess I could simply fully
> specify a URL for the rmap.
>

You don't need to fully specify the URL in the cquery, a relative
location works just fine. e.g. put both files in the same location of
the webserver and just use the name of the rmap.

<cq:componentQuery
xmlns:cq="http://www.eclipse.org/buckminster/CQuery-1.0"
resourceMap="your.rmap">

> 2. Is there a way to handle SVN / CVS credentials if cooresponding repos
> haven't already been created? the only way it works for me now is with
> the repos, which means asking the users to put in the svn, which is
> really half the battle.

In my rmap I refer to properties like cvs.user for the SCM username.
These properties are not defined in the rmap, but in the cquery. In my
case use the property user.name as value of cvs.user.
That's a litle environment dependent, but at least for us the
os-username usually matches the SCM username, so this works pretty well.

<?xml version="1.0" encoding="UTF-8"?>
<cq:componentQuery
xmlns:cq="http://www.eclipse.org/buckminster/CQuery-1.0"
resourceMap="your.rmap">
<cq:rootRequest name="org.example.some.feature"
componentType="eclipse.feature"/>
<cq:property key="cvs.user" value="${user.name}" />
</cq:componentQuery>

If for some reason user.name is not the right username for the SCM the
developer can easily adjust the property value in the CQuery Editor.
Given a correct username, Buckminster will either reuse an existing SCM
location, or create a new one with the given username and prompt for the
password.

Best regards,
Johannes
Previous Topic:Repositories updated from rmap
Next Topic:How to find out what feature provides a certain plugin, and what plugins are provided by a feature
Goto Forum:
  


Current Time: Mon Sep 01 22:08:29 EDT 2014

Powered by FUDForum. Page generated in 0.01944 seconds