# 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-887 Status: open Project: perforce-software-sdp Severity: C ReportedBy: daniel_ferrara ReportedDate: 2023/03/02 05:22:53 ModifiedBy: tom_tyler ModifiedDate: 2023/03/02 05:27:07 OwnedBy: tom_tyler Description: mkrep.sh: Clarify which methods the script uses to determine P4TARGET. An explanation from @Tom Tyler of how the P4MASTERPORT value is defined in mkrepo.sh: If the -f <FromServerID> argument is used, which only applies when making a standby of an edge server, then the P4TARGET value is the ExternalAddress configureable associated with the given ServerID. Otherwise, the P4MASTERPORT value defined when you do source /p4/common/bin/p4_vars N. (where N is the SDP instance name; I can see this customer uses the default 1). Sourcing this file, which is the correct way to load the SDP environment, causes the /p4/common/config/p4_1.vars file to be sourced. Customer would like this clarified in the docs themselves: When I tested, I couldn't edit /p4/common/config/p4_1.vars file. If P4MASTERPORT was set with localhost default, is it possible to add a request that add explanation about the P4TARGET of replica server spec setting source? Docs: https://swarm.workshop.perforce.com/projects/perforce-software-sdp/files/main/Server/Unix/p4/common/bin/mkrep.sh Perforce-internal: See: P4-22418 Component: core-unix Type: Feature