# 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: 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.
Job: SDP-303
Status: open
Project: perforce-software-sdp
Severity: C
ReportedBy: wolfmann
ReportedDate: 2018/03/09 14:44:41
ModifiedBy: tom_tyler
ModifiedDate: 2018/03/09 14:44:41
OwnedBy: tom_tyler
Description:
Simplify update of license files to all servers with HMS.
Per email:
---
It would actually be very cool to be able to drop license files into
a secure folder, that would allow HMS to act like a license server...
not in a P4AUTH way, but the server would be automatically renewed
based upon dropping a file in there.
---
Commonly with SDP deployments, licenses are versioned in
/p4/common/config/licenses, and that folder is sync'd to all hosts
with sdp_sync.sh. That 'licenses' folder hasn't been documented
and enshrined as a formal SDP standard yet, but that can be done as
part of implementing this.
Component: hms
Type: Feature