# 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 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:	HI-3

Status:	punted

Project:	perforce_software-helix-installer

Severity:	C

ReportedBy:	tom_tyler

ReportedDate:	2018/04/03 17:26:09

ModifiedBy:	tom_tyler

ModifiedDate:	2019/06/27 12:26:46

OwnedBy:	tom_tyler

Description:
	Fixed issue ignoring rsync failure of depot files.
	
	In at least one case, the Helix Installer was seen to
	suffer rsync failures putting the archive files for the
	Sample Depot in the right place (perhaps due to rsync
	not being installed?).  Installation still reported
	success.
	
	Review: configure_sample_depot_for_sdp.sh

DevNotes:
	2019/06/27 ttyler: Punted. There are two issues here:
	- The rsync failure due to rsync not being installed, a very
	real possibility. This is a non-issue with reset_sdp.sh now
	handling installation of required packages, including rsync.
	- Not catching other causes of rsync exit failure. In the
	context and environment in which the rsync is called locally
	(no remote host), an rsync failure is unlikey unless
	much bigger issues are going on with the machine.  This
	could be worth fixing, but is deprioritized as this script
	spins up demo hardware.

Component:	sample_depot

Type:	Bug