#ALTIUM DESIGNER VERSION CONTROL SOFTWARE#
Printing PDFs on a schematic and marking them up works but having a mechanism to document these notations within the design software definitely levels it up. In the Git ecosystem this is known as commit and push.įigure 1: Putting a project under version controlįigure 2: Committing your changes and pushing to the serverĬomments: One tool needed for collaboration is the ability to share notes with each other in near real time. In Figure 2, simply clicking on “Save to Server” uploads your design to the server (after requesting you to input your comments). For example, in Figure 1 you will see the option to “Make Project Available Online.” What that’s really doing under the hood is initializing a local Git repository, committing, and pushing the changes to a newly created remote repository. Altium 365 has a VCS built in without you ever noticing. Putting all the details in the background makes that transition a lot easier. Moving from network drives to VCS can be complicated enough. Seamless integration within the tool: Not everyone is familiar with Git Bash or SourceTree nor do they want to be. Let’s review each one to understand how Altium 365 meets each need. Now all these features are available to all Altium 365 users. These features that had been lacking in a vanilla version control system started to roll out with the introduction of Altium 365. A component library using a revision scheme.Ability to comment directly on my schematics and layout.Over the years that I’ve been using various version control systems, I found that all the tools lacked a few key features needed for true ECAD collaboration. Using a vanilla version control system should be the baseline, or entry point, for all PCB design projects. How about disaster recovery when someone’s hard drive fails but is relieved to find out that their files are backed up on a server? What about working on different PCs at different times? Consider a production environment where QA needs to track down a specific change from a specific date and time. Using a VCS for the above-mentioned reasons not only help ourselves/team but also our company overall. Hopefully we’ll be getting some sort of meaningful documentation (in the form of comments) for every commit as well. As discussed in Why Use a Version Control System, we’re getting revision history (including file storage) at a bare minimum. We need to first understand what we’re actually getting when we set up a vanilla version control system. In this article we will be reviewing the differences between a vanilla version control system and Altium 365. As discussed in Why Use a Version Control System, we looked at different options ranging for local hard drive storage to sophisticated online revisioning systems. There are all sorts of vanilla version control systems (VCS) out there that people have been using with their PCB design software.
0 kommentar(er)
