# 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: HI-100 Status: closed Project: perforce_software-helix-installer Severity: C ReportedBy: tom_tyler ReportedDate: 2022/06/30 15:31:10 ModifiedBy: tom_tyler ModifiedDate: 2022/07/05 14:36:09 OwnedBy: tom_tyler Description: HISTFILE setting in perforce_bashrc is not cross-Linux portable. === Customer-contributed comments === History is not kept for the perforce user on Ubuntu 20.04 with Helix Core/SDP Default bashrc is setup with history settings that follow: export HISTFILESIZE=5000 export HISTTIMEFORMAT="%Y/%m/%d %Z %H:%M:%S " export HISTFILE="~/.hist/history.$$.$RANDOM" When the shell attempts to write to the HISTFILE, the following error occurs: perforce@aws-p4d1:/home/perforce history -a -bash: history: ~/.hist/history.1029579.575: cannot create: No such file or directory Unfortunately, this error is silent when the history is not manually written and no history is written on shell exit. Updating the bashrc HISTFILE solves this issue: export HISTFILE="$HOME/.hist/history.$$.$RANDOM" Histories are now written and appear as expected. === Research === This has a good explanation - the quoting suppresses expansion of the ~: https://askubuntu.com/questions/1192981/why-isnt-tilde-recognised-as-home-folder-in-this-case Better to fix this removing the quotes, as the HOME variable isn't as reliably set as one would hope. Component: env Type: Bug