Shared resources

[Jensen, Aaron]

We have a common build and automation platform and use Mercurial's sub-repository feature to share it across projects. It works pretty well. We just had to train people to ignore the sub-repository and leave it alone.


-----Original Message-----
From: Mercurial [mailto:mercurial-bounces at selenic.com] On Behalf Of Angel Ezquerra
Sent: Monday, August 31, 2015 10:00 AM
To: מיטל ואלירן <fistel.me at gmail.com>
Cc: Mercurial <Mercurial at selenic.com>
Subject: Re: Shared resources

On Sun, Aug 30, 2015 at 1:10 PM, מיטל ואלירן <fistel.me at gmail.com> wrote:
> Hello,
>  We are thinking of changing our source control tool, and we need a 
> tool that enables us to both have a shared project (let's call it A) 
> for the team that uses source from another shared project (let's call 
> it B), managed by another team.
>
> Is it possible using Mercurial? What happens with shared project A 
> when shared project B changes? We would love to get some information 
> on how this works.
>
> Thanks in advance,
> Meital.

Hi,

mercurial can do this through a feature called "subrepos". It is considered a "feature of last resort" but we have been using it extensively for several years now and it works very well as long as you do not try to do a lot of "history modification" which is not something that you are bound to do until your expertise grows. Once that happens you should be ready to fix any problems that you might face.

You can read up on subrepos here:
https://mercurial.selenic.com/wiki/Subrepository

Cheers,

Angel
_______________________________________________
Mercurial mailing list
Mercurial at selenic.com
https://selenic.com/mailman/listinfo/mercurial