|
The adminstrative share is indeed the correct name.
Let me explain how we have setup our machines for using vbp.
We have 2 build machines, 1 for our daily build and development tasks and one for creating patches that should go directly into the production environment (at short notice).
The build scripts and our storage needs for generated files (except for the source code) is placed on the a network share //server/share$.
If tried using the network share for storing the configuration files of vbp by updating the registry key ConfigFilesPath.
When I do this, the global macro's still read correctly but not always stored correctly (not sure it this happens always or sometimes). If I change back to a local path, everything seems to work correctly again.
Most of the global marco's are initialized by the %read_ini% macro to be initialized.
Note, currently only one system is up and running
|