Stats

  • Locked Locked
  • Replies 2
  • Subscribers 165
  • Views 15564
  • Members are here 0
More Content
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Integration with version control system

marekmat

Hello everyone.

I have been using OrCAD for more than a year now and I think about implementation a version control system. 

So far, I have used gitlab for symbols and footprints and I didn't expect it to work so good. Although symbols are stored in binary files, Gitlab handles them with no problems. There is no issues with creating symbols, pushing and merging. No conflicts at all. Additionaly, I share the libraries with other co-workers. Everyone is capable of commit. That's a plus for Cadence.

But how do you manage your schematic and layout files? Is it any way to do it? I have enough of creating a copy once an hour or more often. 

What's your experience in that topic? What do you think?

  • RFinley

    Will this work?  https://www.flowcad.ch/en/products/floware/data-management/tortoise-svn-integration

    Yeah, I don't turn my machine off at night unless the day's work has been committed and pushed in SVN or Git.  P*DS layout can destroy your ground stitching instantly.  So...

    All layouts, schematics, powerpoint decks are committed.  Sometimes, engineers don't set up the ignores and someone has to keep purging the log files when they reappear.

      

    I personally use GitHub and Git for my scripting efforts with Atlassian's SourceTree as the UI. 

    At work, use WanDisco with SVN, with mirror servers around the world.  

    Someday this startup can look at EDM.  Someday.

  • Wild

    Some people in my Company use perforce.  I've seen it, IMHO it is much easier to use than SVN, Git or Bitbucket, but $$.

Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.