# 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-756 Status: open Project: perforce-software-sdp Severity: C ReportedBy: rwillyoung ReportedDate: 2022/02/21 08:58:45 ModifiedBy: tom_tyler ModifiedDate: 2022/02/27 08:23:17 OwnedBy: rwillyoung Description: p4_vars should have a flag to ignore "Open for write" permission denied errors to facilitate read-only scripting. For read only workflows (create a monitoring service user in the OS) we don't "care" that we can't write to some directories. The extra output in "error" format is not helpful for catching other relevant error data in a script. source /p4/common/bin/p4_vars 1 Perforce server error: open for write: /p4/1/logs/triggers.csv: Permission denied Perforce server error: open for write: /p4/1/logs/errors.csv: Permission denied Perforce server error: open for write: /p4/1/logs/events.csv: Permission denied Perforce server error: open for write: /p4/1/logs/integrity.csv: Permission denied Perforce server error: open for write: /hxlogs/p4/1/frankfurt/logs: Permission denied Perforce server error: open for write: /p4/1/logs/journal: Permission denied Error error: open for write: /p4/1/logs/events.csv: Permission denied Perforce server error: open for write: /p4/1/logs/triggers.csv: Permission denied Perforce server error: open for write: /p4/1/logs/errors.csv: Permission denied Perforce server error: open for write: /p4/1/logs/events.csv: Permission denied Perforce server error: open for write: /p4/1/logs/integrity.csv: Permission denied Perforce server error: open for write: /hxlogs/p4/1/frankfurt/logs: Permission denied Perforce server error: open for write: /p4/1/logs/journal: Permission denied Error error: open for write: /p4/1/logs/events.csv: Permission denied DevNotes: Component: core-unix Type: Feature