# The form data below was edited by swarm-user # 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-27 Status: closed Project: perforce_software-helix-installer Severity: C ReportedBy: tom_tyler ReportedDate: 2019/08/21 21:54:23 ModifiedBy: swarm-user ModifiedDate: 2021/11/14 00:02:39 OwnedBy: tom_tyler Description: Simplify setup of a proxy-only or broker-only SDP server. The Helix Installer is useful for setting up a host that is to be used only for a p4p or p4broker process, but it doesn't do the job completely, and also leaves around cruft. Some things that need doing: * For a proxy, create the /p4/N/cache directory and symlink. * Removed a bunch of stuff only needed when a P4D server is run, .e.g P4ROOT. There should still be /p4/N/logs and /p4/N/tmp directories, but not root, offline_db, depots, and checkpoints directories. * For a proxy, generate a crontab with call to p4pcm.pl. * For a broker, generate a crontab with call to broker_rotate.sh. DevNotes: [2020/01/29 tom_tyler] I tweaked the scope to include setting up a broker-only server. Component: core Type: Feature