|
| Re: Property expansion in advisor nodes? [message #551478 is a reply to message #551452] |
Fri, 06 August 2010 14:52   |
|
Just a thought, but why not check in the cquery on the branch with a hard-coded branchTagPath for the branch that it's
checked into?
- thomas
On 08/06/2010 03:29 PM, Peter Kullmann wrote:
> Hi,
>
> I'd like to do something like this:
> <cq:advisorNode namePattern="ch.arenae.b.*"
> componentType="osgi.bundle"
> branchTagPath="${mytag}">
> </cq:advisorNode>
>
> and define the property mytag from outside as a system property:
> mytag = R1_0_maintenance
>
> or for a release build we would set
> mytag = /R1_0_1
>
> It seems as if property expansion in advisor nodes or in the
> branchTagPath attribute is not supported. Is this so (or am I doing
> something wrong)? How can I specify a tag for a special build without
> changing my cquery?
>
> Thanks
> Peter
|
|
|
| Re: Property expansion in advisor nodes? [message #551565 is a reply to message #551478] |
Sat, 07 August 2010 06:34 |
 Peter Kullmann
Messages: 240
Registered: July 2009 |
Senior Member |
|
|
Yes, that's what I want to do. The problem comes when I want to build a
specific tagged version for a release build.
The way we worked was more or less like this: We develop some new stuff
on trunk. When we're ready to release it we make a branch, say
R1_0_maintenance. The cquery is also branched and we set the
branchTagPath to R1_0_maintenance. With this we can set up nightly
builds of the branch, ie builds that use the head revision of the branch.
After some testing and fixing, we say that the current version of the
branch will be our release 1.0.0 and we tag all the projects on the
branch with R1_0_0. Now, I want to build this 1.0.0 release. For this I
would like to change the cquery to a branchTagPath=/R1_0_0. But I don't
want to check this in. (Right now, a build with branchTagPath=/R1_0_0
will yield the same result as a build with
branchTagPath=R1_0_maintenance, but this will change as soon as someone
checks something into the branch).
Regards,
Peter
Thomas Hallgren schrieb:
> Just a thought, but why not check in the cquery on the branch with a
> hard-coded branchTagPath for the branch that it's checked into?
>
> - thomas
>
> On 08/06/2010 03:29 PM, Peter Kullmann wrote:
>> Hi,
>>
>> I'd like to do something like this:
>> <cq:advisorNode namePattern="ch.arenae.b.*"
>> componentType="osgi.bundle"
>> branchTagPath="${mytag}">
>> </cq:advisorNode>
>>
>> and define the property mytag from outside as a system property:
>> mytag = R1_0_maintenance
>>
>> or for a release build we would set
>> mytag = /R1_0_1
>>
>> It seems as if property expansion in advisor nodes or in the
>> branchTagPath attribute is not supported. Is this so (or am I doing
>> something wrong)? How can I specify a tag for a special build without
>> changing my cquery?
>>
>> Thanks
>> Peter
>
|
|
|
| Re: Property expansion in advisor nodes? [message #553417 is a reply to message #551565] |
Tue, 17 August 2010 13:26 |
Peter Kullmann
Messages: 240
Registered: July 2009 |
Senior Member |
|
|
I'm starting to understand how to do things the buckminster way, I think:
- The cquery is checked in on the branch with the hard coded
branchTagPath as Thomas suggests
- In addition to this advisor node I'm adding a second advisor with a
filter (buildType=RELEASE) and with a branchTagPath=/R1_0_0.
- Defining a new relase will then consist of setting the correct tag in
branchTagPath, committing and tagging the cquery.
Peter
Peter Kullmann schrieb:
> Yes, that's what I want to do. The problem comes when I want to build a
> specific tagged version for a release build.
>
> The way we worked was more or less like this: We develop some new stuff
> on trunk. When we're ready to release it we make a branch, say
> R1_0_maintenance. The cquery is also branched and we set the
> branchTagPath to R1_0_maintenance. With this we can set up nightly
> builds of the branch, ie builds that use the head revision of the branch.
> After some testing and fixing, we say that the current version of the
> branch will be our release 1.0.0 and we tag all the projects on the
> branch with R1_0_0. Now, I want to build this 1.0.0 release. For this I
> would like to change the cquery to a branchTagPath=/R1_0_0. But I don't
> want to check this in. (Right now, a build with branchTagPath=/R1_0_0
> will yield the same result as a build with
> branchTagPath=R1_0_maintenance, but this will change as soon as someone
> checks something into the branch).
>
> Regards,
> Peter
>
> Thomas Hallgren schrieb:
>> Just a thought, but why not check in the cquery on the branch with a
>> hard-coded branchTagPath for the branch that it's checked into?
>>
>> - thomas
>>
>> On 08/06/2010 03:29 PM, Peter Kullmann wrote:
>>> Hi,
>>>
>>> I'd like to do something like this:
>>> <cq:advisorNode namePattern="ch.arenae.b.*"
>>> componentType="osgi.bundle"
>>> branchTagPath="${mytag}">
>>> </cq:advisorNode>
>>>
>>> and define the property mytag from outside as a system property:
>>> mytag = R1_0_maintenance
>>>
>>> or for a release build we would set
>>> mytag = /R1_0_1
>>>
>>> It seems as if property expansion in advisor nodes or in the
>>> branchTagPath attribute is not supported. Is this so (or am I doing
>>> something wrong)? How can I specify a tag for a special build without
>>> changing my cquery?
>>>
>>> Thanks
>>> Peter
>>
|
|
|
Powered by
FUDForum. Page generated in 0.02870 seconds
] 
Search
Help
Register
Login
Home
