
In this example, the lookup table, or dict, uses the GUID as the key and the remote repository (on your remote Git server) as the value. Since Concord Pro uses GUIDs, the repository name/description lies within the Firebird database. The lookup table (also known as the “repo dictionary” in the code) serves as a linker between each Concord Pro Managed Project repository and your target/remote repository. The code is broken down into two pieces: the lookup table and the synchronizer.

We will be walking through an example script and architecture that automates the process of mirroring all the Managed Projects on a Concord Pro server to another Git server. At the time of writing this article, Concord Pro has no way to store all Managed Projects on an external Git server natively. OverviewĪltium Concord Pro uses an internal Git server to store Managed Projects. What we'll setup here can run as a Windows service on your Altium Concord Pro server.


In this article, we will review an approach that automates creation of a Git server mirror and includes comprehensive logging. In Linking Managed Projects with your Git Server using Altium Concord Pro, we reviewed how to mirror Git repositories from your Altium Concord Pro™ server to your favorite Git server (i.e., Github, Bitbucket, Gitlab, etc.). Altium Concord Pro™ as a standalone product and brand name has been discontinued and the capabilities are now available as part of our Altium enterprise solutions.
