Home » Archived » Buckminster » Resolving versions to subversion tags
|
| Re: Resolving versions to subversion tags [message #436287 is a reply to message #430271] |
Thu, 30 July 2009 22:48   |
 Henrik Lindberg
Messages: 2509
Registered: July 2009 |
Senior Member |
|
|
You do this by modifying the CQUERY. The RMAP entries for SVN repos
should appoint the trunk. The module before/after branch/tag info in the
RMAP is used to figure out where components are found in relationship to
the trunk, a branch or a tag. It does not say anything about which of
these to use - that is done in the CQUERY. The default is to pick from
trunk (i.e. latest).
This is called "Selection Criteria" in the CQUERY. It is documented in
the Buckminster Book (p 52 in version 0.5). Look at the "Branch/Tag
path" (p 53) which controls how Buckminster searches for a component
among branches, tags, and trunk. Text for "branch/tag path" says the
following:
"The branch tag path is used to define a search path. The branches and
tags in this comma separated list are searched in the specified order.
Branches are entered by simply stating their name, and tags are entered
with a leading slash ‘/’ character. The special keyword ‘main’ is used
to refer to the repositories notion of main branch (e.g. ‘trunk’ for
SVN, ‘head’ for CVS, etc.). As an example ‘bug17,/release3,main’ would
first look for the component on branch ‘bug17’, and if not found there,
look in the tag ‘release3’, and finally if not found there either, look
in the repository’s main branch."
Regards
- hnrik
Tas Frangoullides wrote:
> Hi,
>
> I know have a buckminster build working for an RCP product, but this is
> always bulding the latest code. I now want to be able to look for the
> source at an appropriate tag. How do I configure my svn reader so that
> it uses a particular tag? At first I thought the moduleAfterTag type
> queries might provide automatic support but it doesn't work for. My
> initial attempt bellow doesn't work but it give you an idea of what I am
> trying to achieve.
>
>
> <searchPath name="com.mialos.tutorial">
> <provider readerType="svn"
> componentTypes="osgi.bundle,eclipse.feature,buckminster" mutable="true"
> source="true">
> <uri
> format=http://192.168.1.75/svn/sandbox/tutorial/trunk/{0}>
> <bc:propertyRef key="buckminster.component" />
> </uri>
> <provider readerType="svn"
> componentTypes="osgi.bundle,eclipse.feature,buckminster" mutable="true"
> source="true">
> <uri
> format="http://192.168.1.75/svn/sandbox/tutorial/tags/{0}/{1}">
> <bc:propertyRef key="buckminster.component.version" />
> <bc:propertyRef key="buckminster.component" />
> </uri>
> </provider>
> </searchPath>
>
>
>
> Also, did this feature ever get implemented. It would be useful but I
> tried it and it didn't work.
> http://dev.eclipse.org/newslists/news.eclipse.tools.buckmins ter-dev/msg00416.html
>
>
> Thanks,
> Tas
|
|
|
| Re: Resolving versions to subversion tags [message #442755 is a reply to message #436287] |
Fri, 31 July 2009 13:30 |
Tas Frangoullides
Messages: 195
Registered: July 2009 |
Senior Member |
|
|
Hi Henrik,
Thanks. I got this to work now.
It raises a question for me though regarding the tagging and release
procedure. At present I have a project alongside all the other in the
repository trunk callled com.*.*.releng. Here I keep my target platofrm
cquery, and mspec along with the applications cquery. Up until this point it
didn't specify any branch or tag so trunk was used which is fine. I expect
that prior to making a release I would create a tag and then use this to
make releases, starting with the checking out of the com.*.*.releng project.
However, becuase the tag is specified in the cquery I would either need to
edit the cquery after it is check out. Or I could make the change to the
cquery before tagging everything, and then change it back on trunk.
This all adds extra steps which develops have to remember. Do you have any
suggestions or best-practice to reduce the steps necessary (and opportunity
for mistakes).
Thanks,
Tas
"Henrik Lindberg" <henrik.lindberg@cloudsmith.com> wrote in message
news:h4t80l$knm$1@build.eclipse.org...
> You do this by modifying the CQUERY. The RMAP entries for SVN repos should
> appoint the trunk. The module before/after branch/tag info in the RMAP is
> used to figure out where components are found in relationship to the
> trunk, a branch or a tag. It does not say anything about which of these to
> use - that is done in the CQUERY. The default is to pick from trunk (i.e.
> latest).
>
> This is called "Selection Criteria" in the CQUERY. It is documented in the
> Buckminster Book (p 52 in version 0.5). Look at the "Branch/Tag path" (p
> 53) which controls how Buckminster searches for a component among
> branches, tags, and trunk. Text for "branch/tag path" says the following:
>
> "The branch tag path is used to define a search path. The branches and
> tags in this comma separated list are searched in the specified order.
> Branches are entered by simply stating their name, and tags are entered
> with a leading slash ‘/’ character. The special keyword ‘main’ is used to
> refer to the repositories notion of main branch (e.g. ‘trunk’ for SVN,
> ‘head’ for CVS, etc.). As an example ‘bug17,/release3,main’ would first
> look for the component on branch ‘bug17’, and if not found there, look in
> the tag ‘release3’, and finally if not found there either, look in the
> repository’s main branch."
>
> Regards
> - hnrik
>
>
>
> Tas Frangoullides wrote:
>> Hi,
>>
>> I know have a buckminster build working for an RCP product, but this is
>> always bulding the latest code. I now want to be able to look for the
>> source at an appropriate tag. How do I configure my svn reader so that it
>> uses a particular tag? At first I thought the moduleAfterTag type queries
>> might provide automatic support but it doesn't work for. My initial
>> attempt bellow doesn't work but it give you an idea of what I am trying
>> to achieve.
>>
>>
>> <searchPath name="com.mialos.tutorial">
>> <provider readerType="svn"
>> componentTypes="osgi.bundle,eclipse.feature,buckminster" mutable="true"
>> source="true">
>> <uri
>> format=http://192.168.1.75/svn/sandbox/tutorial/trunk/{0}>
>> <bc:propertyRef key="buckminster.component" />
>> </uri>
>> <provider readerType="svn"
>> componentTypes="osgi.bundle,eclipse.feature,buckminster" mutable="true"
>> source="true">
>> <uri
>> format="http://192.168.1.75/svn/sandbox/tutorial/tags/{0}/{1}">
>> <bc:propertyRef key="buckminster.component.version" />
>> <bc:propertyRef key="buckminster.component" />
>> </uri>
>> </provider>
>> </searchPath>
>>
>>
>>
>> Also, did this feature ever get implemented. It would be useful but I
>> tried it and it didn't work.
>> http://dev.eclipse.org/newslists/news.eclipse.tools.buckmins ter-dev/msg00416.html
>> Thanks,
>> Tas
|
|
|
| Re: Resolving versions to subversion tags [message #444312 is a reply to message #442755] |
Fri, 31 July 2009 16:48 |
Henrik Lindberg
Messages: 2509
Registered: July 2009 |
Senior Member |
|
|
You may want to keep one query per release in your releng component in
addition to the developer.cquery (or whatever) you use for "development
on head/trunk". This way, anyone can build any release (without having
to edit anything).
regards
- henrik
Tas Frangoullides wrote:
> Hi Henrik,
>
> Thanks. I got this to work now.
>
> It raises a question for me though regarding the tagging and release
> procedure. At present I have a project alongside all the other in the
> repository trunk callled com.*.*.releng. Here I keep my target platofrm
> cquery, and mspec along with the applications cquery. Up until this
> point it didn't specify any branch or tag so trunk was used which is
> fine. I expect that prior to making a release I would create a tag and
> then use this to make releases, starting with the checking out of the
> com.*.*.releng project. However, becuase the tag is specified in the
> cquery I would either need to edit the cquery after it is check out. Or
> I could make the change to the cquery before tagging everything, and
> then change it back on trunk.
>
> This all adds extra steps which develops have to remember. Do you have
> any suggestions or best-practice to reduce the steps necessary (and
> opportunity for mistakes).
>
> Thanks,
> Tas
>
> "Henrik Lindberg" <henrik.lindberg@cloudsmith.com> wrote in message
> news:h4t80l$knm$1@build.eclipse.org...
>> You do this by modifying the CQUERY. The RMAP entries for SVN repos
>> should appoint the trunk. The module before/after branch/tag info in
>> the RMAP is used to figure out where components are found in
>> relationship to the trunk, a branch or a tag. It does not say anything
>> about which of these to use - that is done in the CQUERY. The default
>> is to pick from trunk (i.e. latest).
>>
>> This is called "Selection Criteria" in the CQUERY. It is documented in
>> the Buckminster Book (p 52 in version 0.5). Look at the "Branch/Tag
>> path" (p 53) which controls how Buckminster searches for a component
>> among branches, tags, and trunk. Text for "branch/tag path" says the
>> following:
>>
>> "The branch tag path is used to define a search path. The branches and
>> tags in this comma separated list are searched in the specified order.
>> Branches are entered by simply stating their name, and tags are
>> entered with a leading slash ‘/’ character. The special keyword ‘main’
>> is used to refer to the repositories notion of main branch (e.g.
>> ‘trunk’ for SVN, ‘head’ for CVS, etc.). As an example
>> ‘bug17,/release3,main’ would first look for the component on branch
>> ‘bug17’, and if not found there, look in the tag ‘release3’, and
>> finally if not found there either, look in the repository’s main branch."
>>
>> Regards
>> - hnrik
>>
>>
>>
>> Tas Frangoullides wrote:
>>> Hi,
>>>
>>> I know have a buckminster build working for an RCP product, but this
>>> is always bulding the latest code. I now want to be able to look for
>>> the source at an appropriate tag. How do I configure my svn reader so
>>> that it uses a particular tag? At first I thought the moduleAfterTag
>>> type queries might provide automatic support but it doesn't work for.
>>> My initial attempt bellow doesn't work but it give you an idea of
>>> what I am trying to achieve.
>>>
>>>
>>> <searchPath name="com.mialos.tutorial">
>>> <provider readerType="svn"
>>> componentTypes="osgi.bundle,eclipse.feature,buckminster" mutable="true"
>>> source="true">
>>> <uri
>>> format=http://192.168.1.75/svn/sandbox/tutorial/trunk/{0}>
>>> <bc:propertyRef key="buckminster.component" />
>>> </uri>
>>> <provider readerType="svn"
>>> componentTypes="osgi.bundle,eclipse.feature,buckminster" mutable="true"
>>> source="true">
>>> <uri
>>> format="http://192.168.1.75/svn/sandbox/tutorial/tags/{0}/{1}">
>>> <bc:propertyRef key="buckminster.component.version" />
>>> <bc:propertyRef key="buckminster.component" />
>>> </uri>
>>> </provider>
>>> </searchPath>
>>>
>>>
>>>
>>> Also, did this feature ever get implemented. It would be useful but I
>>> tried it and it didn't work.
>>> http://dev.eclipse.org/newslists/news.eclipse.tools.buckmins ter-dev/msg00416.html
>>> Thanks,
>>> Tas
>
|
|
|
Goto Forum:
Current Time: Wed Jan 15 20:31:42 GMT 2025
Powered by FUDForum. Page generated in 0.02881 seconds |
] 
Search
Help
Register
Login
Home
