[Anthill-pro] Secondary Workflows and Labels

[Curtis Yanko]

I am trying to sort the issue of applying a label from a non-originating 
workflow. The idea being that we do create and assign a BLD label for each 
build but we consider these builds to be throw away items. I even want to 
go so far as putting those label in a subdirectory of 'tags' since they 
have a low signal-to-noise ratio.

However, when we chose to run a Deploy WF against a an existing Build Life 
and want to go back and apply a REL label to that build.

So I'm looking at the Remote Label step and trying to fugue out which 
beanshell scripts I might need and whether or not having my BLD label in a 
sub-directory would have any impact on my process. Do I need two Source 
configurations? One for my branch with 'tags' and another with 
'tags/build' for the tags URL? Or can I define two modules where each 
references the same branch but two different Tags URL's?

Or can I just the one Source config and preface a tag    /builds/{$STAMP} 
for my Dev Stamp style? and do the same thing when referencing it in the 
SVN remote label step for 'Replace Label'?



- Curtis Yanko
UnitedHealth Group IT
Mail Route: CT028-06SA
Internet email: curt_yanko at uhc.com
Office 860.702.9059
Cell 860.729.8171


This e-mail, including attachments, may include confidential and/or 
proprietary information, and may be used only by the person or entity to 
which it is addressed. If the reader of this e-mail is not the intended 
recipient or his or her authorized agent, the reader is hereby notified 
that any dissemination, distribution or copying of this e-mail is 
prohibited. If you have received this e-mail in error, please notify the 
sender by replying to this message and delete this e-mail immediately.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.urbancode.com/pipermail/anthill-pro/attachments/20070802/ea31a204/attachment.htm