[Anthill-pro] using two different svn repositories

[Samuel Cameron]

If you must have two different repositories, you could create two
workflows. Have the second workflow depend on the first and always start
when the first one finishes. This is not ideal, but better than doing
manual steps.

 

Sam Cameron

 

________________________________

From: anthill-pro-bounces at lists.urbancode.com
[mailto:anthill-pro-bounces at lists.urbancode.com] On Behalf Of Steve
Boone
Sent: Friday, April 11, 2008 11:43 AM
To: AnthillPro user and support list.
Subject: Re: [Anthill-pro] using two different svn repositories

 

Why is the source for one project in two different repositories?  

I would think that would cause many different issues.  Generally, the
code for a project, is all stored in the same place.  That makes keeping
track of the branches, tags, etc much more reasonable and cleaner.  

On Wed, Apr 9, 2008 at 12:21 PM, emerson cargnin
<echofloripa.yell at gmail.com> wrote:

Hi

Is there any plan to allow the use of two different repository
locations (both of the same type) in the same workflow? I'm havin gto
do a half deploy manually because I can't do it in one go with a
single workflow. If i separate it into another workflow then my deploy
workflow (based on the first one) won't pick this up. A second option
would be to add a job to run a shell and run an svn co manually, but I
think this will end up been really complicated if I want to enable
branches, tags, etc to be used...

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

 

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