# 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 given job 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/Doc/Feature/Problem]. Required. # # Bug: is a problem that is fairly well understood, # e.g. one for which there is a reproduction or clear # articulation of the problem. # # Doc: A Documentation fix. # # Feature: An enhancement request, perhaps adding # a new product features, improving maintainability, # essentially any new software improvement other than # a fix to something broken. # # Problem: a 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-894 Status: open Project: perforce-software-sdp Severity: C ReportedBy: tom_tyler ReportedDate: 2023/03/30 17:27:52 ModifiedBy: tom_tyler ModifiedDate: 2023/03/30 17:28:21 OwnedBy: mark_zinthefer Description: For Windows SDP, add docs to add P4Diag autostart. See: https://portal.perforce.com/s/article/17317 The binary is here: http://ftp.perforce.com/perforce/tools/p4diag/bin.ntx64/ The mission: Update the SDP Guide (Windows) to describe how to add P4DIAG Autostart to the SDP installation. With SDP, we know the p4s.exe lives in C:\p4\N\bin, and the P4DIAGLOG should be C:\p4\N\logs\p4diag_log.txt (or similar). So we'll need to do something like: p4 set -S p4_N P4DIAGLOG=C:\p4\N\logs\p4diag_log.txt DevNotes: To Do: * Test that the install works in a lab. * Get it to work, test it. At least see if the log gets generated when the service starts. Then crash the service somehow (???) and see if P4Diag catches it. * Update docs as needed for SDP install on Windows. * For extra credit: Update the Python code that sets up the SDP on Windows to include this. Component: core-win Type: Feature