Almost two years ago we in Advania decided to start using GIT as Source Control Management (SCM). We brought Kamil up to Iceland and we kicked off. In Sorens session on NAVTechDays last year we demoed SourceTree as the GIT client for NAV SCM.
Everything we in Advania are doing with SCM is available on GitHub. It is our hope that we can get as many users and companies to use and contribute to this solution.
Over the next coming days and weeks I will be writing here about this tool. I will also be using the GitHub Wiki for some of the information.
Installing AdvaniaGIT will create a folder structure on your local drive. You can select any of the local drive installed. We suggest that the AdvaniaGIT\Workspace folder should be excluded from Windows Defender and that also goes for any GIT folder used.
Refer to the README.md file inside every subfolder for more details about each subfolder usage.
Inside the Data subfolder we store the module settings in JSON files.
- BranchSettings.json is automatically managed by the module and used to link GIT branches to local NAV environments.
- BuildSettings.json contains incremented values that will be used when building new environments.
- GITSettings.json contains machine settings for the module.
- NAVVersions.json contains information about locally installed NAV.
- RemoteSettings.json contains settings for the Remote Management module. Not used by GIT in any way.
- TenantSettings.json contains settings for each tenant running on a remote server that is managed using the Remote Management module. Not used by GIT in any way.
In the GIT repository folder we require a setup.json file. When the scripts are executed settings from the GIT branch (setup.json) and settings from the machine (GITSettings.json) are merged to a single settings object. If same settings exist in both files the one in the GIT branch will be used.
Installing the module will add custom actions to SourceTree and a command file (StartPowerShell.cmd) to your Windows directory. SourceTree will execute this command file with parameters telling the module what to do. The command file will execute Scripts\Start-CustomAction.ps1 with the same parameters. All custom actions within the Scripts\CustomActions subfolder can be executed.
For teams we suggest using a FTP server for backups and CRONUS text files.
My next blog post will be on the installation and update of AdvaniaGIT. Stay tuned…
2 Replies to “Introducing AdvaniaGIT – SCM for Dynamics NAV”
Looks really interesting. Making NAV development better
Hi Gunnar, Good work! Looking forward to be trying it out! 🙂