CheckFixes.yaml #3

  • //
  • guest/
  • perforce_software/
  • sdp/
  • main/
  • Server/
  • Unix/
  • p4/
  • common/
  • bin/
  • triggers/
  • CheckFixes.yaml
  • View
  • Commits
  • Open Download .zip Download (2 KB)
# This is the config file for the trigger CheckFixes.py
# It defines the error message, the allowed states when jobs can be linked to and the field
# to check for those state values.
#
# Please refer to Workflow.yaml in this directory for a cross-trigger example which could easily
# incude the fields below as well as other fields for other triggers.
#
# It is a standard Yaml format - when in doubt put quotes around string values!

# fix_state_field: the name of the field in the Perforce job spec
fix_state_field: "JiraStatus"

# link_allowed_states: An array of values for fix_state_field in which links are allowed to be created
# or deleted between jobs and changelists
fix_allowed_states:
  - "Accepted"

# msg_cant_link_jobs: An array of lines for the message
# For legibility it is good to have the first line blank
msg_cant_link_jobs:
  - ""
  - "You are not allowed to link changes to or unlink changes from these jobs"
  - "because of the state of their associated JIRA issues."
  - "Please change the state first in JIRA and try again."

# Projects - an array of project entries
# Each project expected to have entries for:
# depot_paths: an array of values for which to process other fields
#     Controlling here allows you to not have to update the trigger table entry every
#     time you wish to adjust. Also, it is possible to have this file be updated by ordinary
#     users and not just superusers. You can even auto-sync this file if required via trigger.
#     Use quotes if spaces in the path, or if you have an exclude mapping ("-//some/path/...")
# fix_allowed_paths: an array of depot paths for which the CheckFixes.py checkes shown above
#     does not apply. This allows integrators to copy up changes (thus creating a new submit),
#     even when the associated issue is closed. Specify one or more paths with wildcards where
#     you will let submits to be handled.
#     Same rules for quoting as for depot_paths, and exclude mappings also possible
#     If field empty or not present then there are no exclusions
projects:
  - name:                       ProjectA
    depot_paths:
      - //depot/inside/...
      - "-//depot/inside/....c"
    fix_allowed_paths:
      - //depot/inside/rel/...
# Change User Description Committed
#4 27331 C. Thomas Tyler Released SDP 2020.1.27325 (2021/01/29).
Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'.
#3 25245 C. Thomas Tyler Released SDP 2019.1.25238 (2019/03/02).
Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'.
#2 23510 C. Thomas Tyler Released SDP 2018.1.23504 (2018/01/19).
Copy Up using 'p4 copy -r -b perforce_software-sdp-dev',
with selective removal of work-in-progress files.
#1 23331 C. Thomas Tyler Released SDP 2017.4.23329 (2017/12/05).
Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'.
//guest/perforce_software/sdp/dev/Server/Unix/p4/common/bin/triggers/CheckFixes.yaml
#1 23158 Robert Cowham Yaml config file from last change