# 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. # # Component: Larger projects may use this optional field to # indicate which component of the project a given # job is associated with. # # Type: Type of job [Bug/Feature]. Required. Job: CBD-26 Status: suspended Project: perforce-software-cbd Severity: B ReportedBy: tom_tyler ReportedDate: 2017/05/17 12:18:57 ModifiedBy: tom_tyler ModifiedDate: 2017/06/06 06:20:19 OwnedBy: tom_tyler Description: Fix ticket issues: Do 'p4 login' if necessary. Presently, the CBD automation presumes it has a valid ticket. Add a 'p4 login -s' ticket status check, and if it fails, attempt a 'p4 login' using credentails available via a mechanism similer to that used by the SDP to ensure checkpoints run reliably. This check needs to be added to BOTH the update trigger and the broker filter script. This change will increase the coupling betweeen CBD and the SDP, which has been kept to a minimum thus far. That's acceptable. DevNotes: Suspended this job on 2015/06/25. This would make CBD more robust, but a reason to avoid fixing this is that having broken tickets on the server is a bigger problem, and 'fixing' this for CBD would mask the root cause. Tickets on a server should be completely reliable to benefit all automation on the Helix server, with CBD triggers and broker filter scripts just being one example. A counter point: CBD automation is used almost constantly, so even if is viewed as a workaround to some unrelated problem with tickets being broken on the server, it's probably going to be an effective workaround. Type: Feature