# 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/Problem].  Required.
#                 Feature and Bug are common terms.
#                 A Problem is suspected bug, or one without a clear
#                 understanding of exactly what is broken.
#
#  Release:       Release in which job is intended to be fixed.

Job:	HI-85

Status:	suspended

Project:	perforce_software-helix-installer

Severity:	C

ReportedBy:	tom_tyler

ReportedDate:	2021/12/10 09:53:03

ModifiedBy:	tom_tyler

ModifiedDate:	2022/01/12 09:38:04

OwnedBy:	tom_tyler

Description:
	Enhance Helix Installer to run with limited sudo.
	
	If a new '-mkrep' option is given, meaning the Helix Installer
	is called by the SDP mkrep.sh as part of the machine boot-strapping
	process, certain behaviors apply.
	
	If we run with limited sudo, what needs to be defined ahead
	of time, e.g. baked into a baseline VM image? Things such as:
	
	* The 'perforce' OS user must exist and already be configured w/sudo.
	* The 3 /hx* (or equivalent) directories must exist.
	* The '-no_ppr' is needed.
	* The '-fast' is needed.

DevNotes:
	2022-01-12 ttyler: Suspended this job, as the need for it has become
	obsolete.

Component:	core

Type:	Feature