[Anthill-pro] using two different svn repositories

[emerson cargnin]

The other repository is a mirror of a CMS tool that we use. Some parts of
our website are kept on that.

This second repository are owned by the content team, so it makes sense to
sit in a different place.
What I did was to create a separated project that I can fetch and deploy to
any server those cms pages.
As the changes on this follow a different schedule and it has pages of the
website it actually isn't desired to be automatically deployed with the main
workflow.

Thanks for the answers of all
Emerson


On 11/04/2008, Alexandre Borgia <alexandre.borgia at ubisoft.com> wrote:
>
>  We have the same situation here as well … in our case it is logical to
> use the different repositories in different workflows so it is not much of a
> problem, except when it comes to the build-scripts/tools we use for
> building.  They are all centralized in the same repository and we must
> deploy them using a custom sync step when we are not working on this one.
>
>
>
>             - Alexandre Borgia
>
>
>  ------------------------------
>
> *De :* anthill-pro-bounces at lists.urbancode.com [mailto:anthill
> -pro-bounces at lists.urbancode.com] *De la part de* Eric Minick
> *Envoyé :* 11 avril 2008 18:17
> *À :* AnthillPro user and support list.
> *Cc :* AnthillPro user and support list.
> *Objet :* Re: [Anthill-pro] using two different svn repositories
>
>
>
> An "always force" pull dependency wouldn work as well. You would just have
> to trick re two related workflows into running on The same machine.
>
>
> On Apr 11, 2008, at 2:57 PM, "Samuel Cameron" <
> Samuel.Cameron at marketlive.com> wrote:
>
>  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<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>
> 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>Anthill-pro at lists.urbancode.com
> <http://lists.urbancode.com/mailman/listinfo/anthill-pro>
> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>
>  _______________________________________________
> Anthill-pro mailing list
> Anthill-pro at lists.urbancode.com
> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>
>
> _______________________________________________
> 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/20080413/891b4893/attachment.htm