# The form data below was edited by ronprestenback
# 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: P4XFER-9
Status: open
Project: perforce-software-p4transfer
Severity: B
ReportedBy: ronprestenback
ReportedDate: 2019/04/24 10:01:26
ModifiedBy: ronprestenback
ModifiedDate: 2019/04/24 10:01:26
OwnedBy: ronprestenback
Description:
Script doesn't handle cases where archive file is missing from the p4 server
If an archive file is missing from the p4 server, calls to 'p4 sync' will throw an exception similar to:
[Error]: 'Librarian checkout f:\\depot-main\\dev/sound/banks/foley/stone.bank failed.\nopen for read: f:\\depot-main\\dev/sound/banks/foley/stone.bank,d\\1.472161.gz: The system cannot find the file specified. '
Consider providing an option to enable handling this case similar to purged files (create dummy file to use in place of revision)
DevNotes:
Type: Bug