# The form data below was edited by robert_cowham # 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]. Required. # # Release: Release in which job is intended to be fixed. Job: SDP-198 Status: closed Project: perforce-software-sdp Severity: C ReportedBy: amo ReportedDate: 2017/04/02 17:32:58 ModifiedBy: robert_cowham ModifiedDate: 2020/08/15 09:57:57 OwnedBy: amo Description: DOC: SDP Guide needs more detail on SDP-controlled replica setup. Following the SDP Guide to set up an SDP-controlled replica. On page 20 of 36 it explains how you seed the replica's database from checkpoint, then log in the service user to create a tickets file. The latter might need additional clarification. Recovering from checkpoint does not recreate the tickets file. This is created when the user runs 'p4 login', or you create the tickets file manually. The commands I found to work are not quite as written; I used: export P4TICKETS=/p4/1/.p4tickets p4 -u svc_replica1 -p svrmaster:1667 login Restoring the checkpoint, the 'p4d -jr' command, creates the database that your replica server instance will use. Before you start this server instance, your service user needs a valid ticket. You create the ticket using 'p4 login' and make sure it's in the P4TICKETS file - this is the 'export/p4 login' commands. Technically, these are independent events - you can create the database first then the ticket, or the other way around - but both need to be completed on the replica server before you attempt to start the server instance. Please consider updating the docs to provide this additional clarity! DevNotes: Job re-opened to address mkrep.sh specifically. Component: doc Type: Bug