# 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-541 Status: closed Project: perforce-software-sdp Severity: C ReportedBy: tom_tyler ReportedDate: 2020/06/02 14:37:58 ModifiedBy: tom_tyler ModifiedDate: 2022/03/26 19:32:39 OwnedBy: tom_tyler Description: Make 'p4d' rather than 'p4d_N' safe to run. The SDP supports having multiple instances running on the same server machine, and thus the admin must always be aware of which instance they are using. SDP docs advise using 'p4d_N', where N is the instance name, rather than simply calling 'p4d'. That ensures you get the correct p4d version for that instance, and also applies the '-C1' if required for a given instance. However, because calling 'p4d_N' rather than simply 'p4d' is at odds with Core docs, KB articles, and Support recommendations, it can cause confusion and contribute to where the wrong 'p4d' version is inadvertantly called. === Proposed New Behavior === 1. The file /p4/common/bin/p4d, which is currently the latest p4d binary staged for the next planned upgrade of any instance, will be replaced with a wrapper script. If the $SDP_INSTANCE environment variable is defined as N, the 'p4d' script will call /p4/N/bin/p4d_N, thus making SDP operations more consistent with core docs and a plethora of KB articles. If $SDP_INSTANCE is undefined, it will exit with a useful error message. 2. The 'verify_sdp.sh' will find *any and all* 'p4d' binaries in the path, and report them as errors. This will include /p4/common/bin/p4d, and also any other errant ones, e.g. in /usr/local/bin, /usr/bin, /usr/sbin/, /opt/perforce/bin, etc. Any binary name 'p4d' will be deemed an error if found on the path. 3. The 'mdkirs.sh' and 'upgrade.sh' scripts, as well as the Helix Installer, will be updated accordingly. 4. SDP docs will be updated accordingly. 5. The 'upgrade_sdp.sh' script (not yet in the SDP) will fix this when upgrading SDP. Component: core-unix Type: Feature