What paths within the DeployStudio components would be useful to keep track of changes in?
DeployStudio's mpkg is a bundle-style distribution package that contains several packages. All the various shell scripts and configuration files seem to exist within the DeployStudio Admin app bundle at:
DeployStudioServer_vX.Y.Z.mpkg/Contents/Packages/deploystudioAdmin.pkg
Here are several useful top-level paths that could be useful to track:
Contains the sys_builder script and its components used to build NBIs. Frequently updated for fix NBI-related issues.
Source of scripts used for all DeployStudio workflow tasks.
Some other core components shared between Admin and Runtime.
Without any kind of file type filtering these will include things like image resources, etc. but these are unlikely to change frequently and so will not clutter up diffs too significantly. We'd be sure that we wouldn't accidentally filter out files that would be useful to see changes (or new files created), and while it's certain this would also include binary files, these could be also be useful to have at hand for comparison.
Are there any other paths we should track?
And yes, the plan would be to run this on nightly builds - stable builds are very rare.
In its current state, the run script can take arbitrary versions in addition to the latest stable or nightly, making it easy to trigger a complete rebuild of the Git repo and tags for all installers available on the DS downloads index.