SDP-564

C. Thomas Tyler
Closed
Normalized SDP Versioning will start in the SDP r20.1 release.

The Version file included in the package, /p4/sdp/Version, will
be enshrined as the standard and easy way to determine the SDP
version.

Starting in the SDP r21.1 release, the upgrade_sdp.sh script (new
in the r20.2 release) will upgrade this Version file.

The verify_sdp.sh script will be updated to require ths file to
exist. A successful verfify_sdp.sh run will be required before
uprade_sdp.sh (coming in r21.1) will start upgrade processing.

See: SDP-540 - Add upgrade_sdp.sh script to the SDP.
Status
Closed
Project
perforce-software-sdp
Severity
C
Reported By
tom_tyler
Reported Date
Modified By
swarm-user
Modified Date
Owned By
tom_tyler
Dev Notes
This job evolved. Originally there was going to be a new /p4/Version
file, but this idea was dropped.  The /p4/sdp/Version is clear enough.

The spirit of this job, which is to standardize and simplify SDP version
checking, is upheld. It was determined that adding yet antoher copy of
the Version file would not help with this.

This does mean the SDP 'tarball extraction' folder that is symlinked from
/p4/sdp is now required on all SDP machines.  This is reasonable and it
does match how SDP is commonly deployed. There is a failure mode where
copying SDP from one machine to another (e.g. via rsync) might miss this,
however the verify_sdp.sh will catch that.
Component
setup
Type
Feature