# 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-731 Status: closed Project: perforce-software-sdp Severity: A ReportedBy: tom_tyler ReportedDate: 2022/01/20 14:30:44 ModifiedBy: tom_tyler ModifiedDate: 2022/01/21 12:01:32 OwnedBy: tom_tyler Description: referesh_P4ROOT_from_offline_db.sh should abort if p4d is not up at start. DevNotes: 2022-01-21 This was originally filed , but turns out the description was incorrect. The script does indeed have correct logic already to abort if p4d is not up at the start. This is not an issue in the current SDP. However, for the 2019.3 SDP, bug SDP-575 was still in play, and there could be problems where referesh_P4ROOT_from_offline_db.sh does the wrong thing. The fix is to upgrade to SDP 2021.2. Closing this job with no code change. Component: core-unix Type: Bug