SDP-665
Suspended
When we run upgrade.sh the script will output errors due to not having certain configurables set:
Error: No value defined for configurable [any:journalPrefix].
Error: No value defined for configurable [any:server.depot.root].
Should these really be checked at the 'any' level? Maybe we're unique, but we set these on a per-instance basis because the path names contain the instance names. E.g. /p4/sdptest/depots or /p4/sdptest-backup/depots.
Looking at //guest/perforce_software/sdp/dev/Server/setup/configure_new_server.sh it does appear to set these at the 'any' level, but that is potentially problematic down the road. E.g. if those paths aren't accessible in a multi-OS environment (having server.depot.root=z:\depot_root then bringing up an instance on Linux).
Error: No value defined for configurable [any:journalPrefix].
Error: No value defined for configurable [any:server.depot.root].
Should these really be checked at the 'any' level? Maybe we're unique, but we set these on a per-instance basis because the path names contain the instance names. E.g. /p4/sdptest/depots or /p4/sdptest-backup/depots.
Looking at //guest/perforce_software/sdp/dev/Server/setup/configure_new_server.sh it does appear to set these at the 'any' level, but that is potentially problematic down the road. E.g. if those paths aren't accessible in a multi-OS environment (having server.depot.root=z:\depot_root then bringing up an instance on Linux).
- Status
- Suspended
- Project
- perforce-software-sdp
- Severity
- C
- Reported By
- Domenic
- Reported Date
- Modified By
- C. Thomas Tyler
- Modified Date
- Owned By
- Domenic
- Dev Notes
- 2021-08-22 ttyler: Changed status from open to suspended, per comments.
- Component
- core-unix
- Type
- Bug