# The form data below was edited by perforce # 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: PSLA-3 Status: open Project: perforce-software-log-analyzer Severity: C ReportedBy: douglasawh ReportedDate: 2018/07/31 07:59:28 ModifiedBy: perforce ModifiedDate: 2019/02/19 10:50:45 OwnedBy: douglasawh Description: Docker instructions flawed Looking at https://swarm.workshop.perforce.com/files/guest/perforce_software/utils/log_analyzer/README.md the docker instructions appear to be flawed (perhaps a newer version of Docker is required?) perforce@dwhitfield-ubuntu2012vsphere:~$ make build docker build -t psla psla docker - version 1.4 Copyright 2003, Ben Jansens <[email protected]> Usage: docker [OPTIONS] Options: -help Show this help. -display DISPLAY The X display to connect to. -border The width of the border to put around the system tray icons. Defaults to 1. -vertical Line up the icons vertically. Defaults to horizontally. -wmaker WindowMaker mode. This makes docker a fixed size (64x64) to appear nicely in in WindowMaker. Note: In this mode, you have a fixed number of icons that docker can hold. -iconsize SIZE The size (width and height) to display icons as in the system tray. Defaults to 24. -color COLOR The background color to use for the tray. Defaults to whatever color the window manager specifies. make: *** [build] Error 1 DevNotes: Type: Bug