# 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]. Required. # # Release: Release in which job is intended to be fixed. Job: SDP-666 Status: suspended Project: perforce-software-sdp Severity: C ReportedBy: Domenic ReportedDate: 2021/07/13 17:04:34 ModifiedBy: tom_tyler ModifiedDate: 2021/08/22 20:41:58 OwnedBy: Domenic Description: There doesn't appear to be a way to do an upgrade via upgrade.sh WITHOUT having a local offline_db setup. It is possible to skip phase 1 (with -M) but there are steps in phases 4 and 5 that reference the offline_db paths and will bail with "Journal rotation failed during offline_db upgrade phase". This means the upgrade won't complete / be considered a success and move on to later steps (i.e. starting the broker) even though p4d is up. It would be great to have a way to skip all the offline_db checks/work, similar to how we can set DoOfflineDBTest=0 in verify_sdp.sh. DevNotes: 2021-08-22 ttyler: Suspended per comments. Component: core-unix Type: Feature