Thanks for your confirmation on using macros as “best practices”.
Without any expectations a summary of my use cases for variables:
A default value is assigned and not changed at runtime. For example Scriptname “D:\Tools\Sometool.exe” or Reportname “MyReport.xml”
Passed by ContinuaCI, for example “BuildBranch”, usually not modified at runtime
Loaded from a configuration file. Directories (no filename) and paths (directory including a filename), usually not modified at runtime
Directories derived by other directories (Root is FBPROJECTDIR), usually not modified after initial assignment
Variables, for example holding version information
I group my variables, according to the above use cases. Maybe the group name can be extended to specify properties that affect the usage of properties belonging to that group.
[X] is path/filename
[X] value retrieved from Continua (arguments)
But maybe it is more flexible to add such properties aside the already known, such as “macro”.