[Anthill-pro] Branching

Tue Apr 3 12:16:38 CDT 2007

I think that is what I use now for Working Directory.

Still, from a scaling standpoint (especially when you add in security) it 
seems like there is too much to do. IMO opinion, I should be able to make 
a copy of one thing and then update which source config it uses and the 
actual numbers used for stamping (in that same place) and then NOT have to 
reset the permission on it.  Sort of the old Project / Build Track idiom.

Perhaps a behind-the-scenes script from you guys could streamline this. My 
concern is that creating support or a branch has to be completely trivial 
if I am to support 100's of projects with 1000's of developers eventually.

- Curtis Yanko
United Health Technologies
Mail Route: CT028-06SA
Internet email: curt_yanko at uhc.com
Office 860.702.9059
Cell 860.729.8171

Ryan Smith <rws at urbancode.com> 
Sent by: anthill-pro-bounces at caladin.urbancode.com
04/03/2007 11:42 AM
Please respond to
rws at urbancode.com; Please respond to
anthill-pro at caladin.urbancode.com

To
"Jeff Rodgers (jerodger)" <jerodger at cisco.com>
cc
anthill-pro at caladin.urbancode.com
Subject
Re: [Anthill-pro] Branching

Thanks for the great addition Jeff!

Here is an example of a working directory script that uses the
workflow's name:

${anthill3/work.dir}/projects/${bsh:PathHelper.makeSafe(ProjectLookup.getCurrent().getName())}/${bsh:PathHelper.makeSafe(WorkflowLookup.getRequested().getName())}

Ryan

Jeff Rodgers (jerodger) wrote:
> You also need to ensure that there is no conflict with your working
> directory. That is, if you are only using the project to name your dir,
> then each branch will end up building in the same dir! Alternatives, a
> lock or a different dir for each branch. But then you have to pass the
> knowledge of the branch name to the working dir script. I didn't know
> how to do that, so I used a lock.
>
>
> Jeff Rodgers
> Cisco Remote Operations Services
>
> -----Original Message-----
> From: anthill-pro-bounces at caladin.urbancode.com
> [mailto:anthill-pro-bounces at caladin.urbancode.com] On Behalf Of Ryan
> Smith
> Sent: Tuesday, April 03, 2007 9:53 AM
> To: anthill-pro at caladin.urbancode.com
> Cc: anthill-pro at caladin.urbancode.com
> Subject: Re: [Anthill-pro] Branching
>
> Curtis,
>
> That is how you would set up a new branch in Anthill. You would create a
> new source config, stamping strategy and workflow.
>
> Ryan
>
> Curtis Yanko wrote:
>
>> All,
>>
>> I am trying to get my head around how we set up for supporting
>> parallel development.
>>
>> So... if I have a project like the XPetstore and I've just made my
>> branch in SVN, what steps do I need to do to support in AHP?
>>
>> My original thought was a new project but now I think a new worklow
>> makes more sense. So I would need to define a new source config, new
>> stamping strategies and a new workflow? Am I missing something?
>>
>> - Curtis Yanko
>> United Health Technologies
>> 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.
>
>> ----------------------------------------------------------------------
>> --
>>
>> _______________________________________________
>> Anthill-pro mailing list
>> Anthill-pro at lists.urbancode.com
>> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>>
>>
>
> --
> ===========================================================
> Ryan Smith.                           2044 Euclid Ave., Suite 600
> Lead Developer                  Cleveland, Ohio 44115
> Urbancode, Inc.
>                                 email:  rws at urbancode.com
> web:     www.urbancode.com      phone:  216-858-9000
> web:     www.anthillpro.com     fax:    216-858-9602
> ===========================================================
>
> _______________________________________________
> Anthill-pro mailing list
> Anthill-pro at lists.urbancode.com
> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>
>

--
===========================================================
Ryan Smith.                     2044 Euclid Ave., Suite 600
Lead Developer                  Cleveland, Ohio 44115
Urbancode, Inc.
email:  rws at urbancode.com
web:     www.urbancode.com      phone:  216-858-9000
web:     www.anthillpro.com     fax:    216-858-9602
===========================================================

_______________________________________________
Anthill-pro mailing list
Anthill-pro at lists.urbancode.com
http://lists.urbancode.com/mailman/listinfo/anthill-pro

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/20070403/3366e87d/attachment.htm