# The form data below was edited by tom_tyler
# Perforce Workshop Jobs
#
# Job: The job name. 'new' generates a sequenced job number.
#
# Status: Job status; required field. There is no enforced or
# promoted workflow for transition of jobs from one
# status to another, just a set of job status values
# for users to apply as they see fit. Possible values:
#
# open - Issue is available to be worked on.
#
# inprogress - Active development is in progress.
#
# blocked - Issue cannot be implemented for some reason.
#
# fixed - Fixed, optional status to use before closed.
#
# closed - Issue has been dealt with definitively.
#
# punted - Decision made not to address the issue,
# possibly not ever.
#
# suspended - Decision made not to address the issue
# in the immediate future, but noting that it may
# have some merit and may be revisited later.
#
# duplicate - Duplicate of another issue that.
#
# obsolete - The need behind the request has become
# overcome by events.
#
# Project: The project this job is for. Required.
#
# Severity: [A/B/C] (A is highest) Required.
#
# ReportedBy The user who created the job. Can be changed.
#
# ReportedDate: The date the job was created. Automatic.
#
# ModifiedBy: The user who last modified this job. Automatic.
#
# ModifiedDate: The date this job was last modified. Automatic.
#
# OwnedBy: The owner, responsible for doing the job. Optional.
#
# Description: Description of the job. Required.
#
# DevNotes: Developer's comments. Optional. Can be used to
# explain a status, e.g. for blocked, punted,
# obsolete or duplicate jobs. May also provide
# additional information such as the earliest release
# in which a bug is known to exist.
#
# Component: Projects may use this optional field to indicate
# which component of the project a givenjob is associated
# with.
#
# For the SDP, the list of components is defined in:
# //guest/perforce_software/sdp/tools/components.txt
#
# Type: Type of job [Bug/Feature/Problem]. Required.
# Feature and Bug are common terms.
# A Problem is suspected bug, or one without a clear
# understanding of exactly what is broken.
#
# Release: Release in which job is intended to be fixed.
Job: SDP-764
Status: open
Project: perforce-software-sdp
Severity: C
ReportedBy: tom_tyler
ReportedDate: 2022/03/04 08:07:42
ModifiedBy: tom_tyler
ModifiedDate: 2022/03/04 08:07:42
OwnedBy: tom_tyler
Description:
Add regression test for sdp_upgrade.sh custom extraction logic.
Detail for the test: Start with an SDP 2020.1 install.
Add P4_MSG="Life" in /p4/common/bin/p4_vars after the '### MAKE LOCAL CHANGES HERE' tag
Add P4_MSG+=" is Good" in /p4/common/config/p4_1.vars after the '### MAKE LOCAL CHANGES HERE' tag
Run sdp_upgrade.sh per usual instructions in https://swarm.workshop.perforce.com/projects/perforce-software-sdp/view/dev/doc/SDP_Guide.Unix.html#_sample_sdp_upgrade_procedure
Success Criteria:
Check that the custom logic is gone from the post-upgrade /p4/common/bin/p4_vars and /p4/common/config/p4_1.vars.
Check that /p4/common/site/config/p4_vars.local and /p4/common/site/config/p4_1.vars.local exist.
Check that sourcing /p4/common/bin/p4_vars 1, doing 'echo P4_MSG=$P4_MSG' reports Life is Good.
Component: core-unix
Type: Feature