svn/git integration, question about libgdm*_sh.so file.

I don't think "a lot of people" have made an integration with svn or git. There is one commercial svn integration - VersIC from MethodICs EDA (who are a Cadence connection partner). There are also four other connection partners who have different Design Management integrations  - ClioSoft (SoS), Dassault (DesignSync), IBM (Clearcase) and IC Manage (IC Manage) - each integrating different version control systems.

I know of one or two customers who have rolled their own GDM integrations - this usually involves a services contract to provide the extra support needed - but this is relatively rare because it's a non-trivial amount of work. You're generally better advised to go with a commercial offering because they will have been through the experiences of fine tuning the integration to ensure it works robustly and well.

A few customers have done basic SKILL-based integrations but these are often rather incompletely integrated and have some holes which make them less attractive. Essentially the tools in that case wouldn't really know about the underlying integration and so this cannot really be recommended.

So my suggestion is that you contact the connection partners I mention above. If you really want to find out more about doing your own via a service, you should contact your account team.

Regards,

Andrew.

We have already working with ClioSoft also considering IC Manage and etc. but all of them have  their "plus" and "minus"

And also only Methodics IC are using SVN and nobody Git.

Simple I thought that it will be good to have own work, with own features for anolog and digital teams and etc.

Of course we will meet with a lot of issues, but maybe it will be interesting project.

But thx for u answer.

IMHO for GIT was created a very interesting code on Skill++ github.com/.../cdsgit

I haven't taken a proper look at this code (I can't really - it has a restrictive license and there's a risk of IP pollution so I have to be careful), but usually most SKILL-based integrations end up making a lot of assumptions about co-managed sets in Virtuoso - often things like the fact that co-managed sets in a cellView can consist of a set of files where files get both added and removed between versions - and you need to ensure that all the related files in the view are managed in a  way that they are seen as a consistent set. How successfully an integration works often depends on those more challenging (but quite frequent) scenarios, particularly with some of the complex multi-file views in Virtuoso.

Having supported numerous customers over the years who have either done GDM integrations or tried to do their own SKILL-based integration (as well as supporting the connections partners in this area), the devil is definitely in the details.

That said, the author of the code often posts here... 

So I would simply say "caveat emptor".

Regards,

Andrew.

Yes, I agree with you. Create own integration will have a lot of challenges with co-managed, soft links and etc.
Simple with my expiries: SOS is no comfortable for digital team and still have a lot of issues with branch working and not friendly with reference projects. IC manage use perforce and jira and to managed generic files we need prepare special "container", with metodics IC need to have plenty of time for discussion to get evaluation version (i spend about 6 month), desing sing as I remember use cvs (but I have no problem with them).

So, thx u again, your tips are always helpful. But if u can give us documentation on GDM API it will be good :)

The GDM API documentation is only provided under a services contract, because we would need to a) give you access to the API and b) ensure that there is a support channel. 

So I certainly can't provide it here. As I mentioned before, you should contact your account team for this.

Regards,

Andrew.

So, I'm understand. Thx. you.