Release Notes for SDP - the Server Deployment Package for the Perforce Server Introduction This document notes major changes to the SDP, in particular those changes which will require extra steps if upgrading a previous SDP installation. SDP is identified by a Version file in the root directory of the SDP package. -------------------------------------------------------------------------- Upgrading the Unix SDP To incorporate a new version of the SDP into an existing SDP installation, first stage the deployment as in this example, assuming you have put the SDP distribution tar file in /depotdata. Working as user root on a Perforce server: cd /depotdata # If an sdp folder exists here, move it aside, e.g. to # sdp.MOVED_2014-09-11 tar -xzpf sdp.Unix.2014.2.10148.tgz chown -R perforce:perforce sdp.Unix.2014.2.10148.tgz /depotdata/sdp cd /depotdata/sdp/Server/Unix/p4/common/bin # Copy 'p4', 'p4d', 'p4broker', 'p4web', 'p4p', etc. (only # those currently used) into this 'bin' folder. cd /depotdata/sdp/Server/Unix/setup vi mkdirs.sh # Review and adjustments to mkdirs.sh suit your environment. ./mkdirs.sh 1 -test Using 'mkdirs.sh' script with the '-test' flag as illustrated above will deploy to the SDP to /tmp/p4 rather than /p4 area. If working on the Production server directly, DO NOT forget to use the '-test' flag. -------------------------------------------------------------------------- Versioning the Unix SDP We strongly recommend that files in the following locations are versioned (in Perforce): /p4//bin /p4/common -------------------------------------------------------------------------- CHANGE HISTORY: SDP/Unix/2014.2/10464 (2014/09/30): Minor adjustments to Maintenance scripts, e.g. fixing typos and adding import sys. Adjusted SDP test Vagrant file comments to account for new home in The Workshop. SDP/Unix/2014.2/10148 (2014/09/11): First release of the Server Deployment Package (SDP), into The Perforce Workshop.