Payload delivered to UVCS triggers

Unity Services
,
1

Hey there,

Building off a previous question, I was wondering if there’s any info on the exact payload that gets delivered to a UVCS trigger.

The input doc vaguely refers to revision specs; meanwhile, the samples shown in the older documentation seem to just parse standard input line by line.

Is there documentation that lays out specifically what will be included in those lines? Is it simply a bit of UVCS metadata and a list of files? A listing of all changed lines?

I’m looking to run a script that can validate the actual contents of files (in a before-clientcheckin trigger), but I’d like to know what’s actually natively available to the trigger to do so.

-n

2

Actually I realised after the fact that the old documentation does indeed show some sample output, e.g.,

CH "/" DIR#br:/main/scm001;changeset:61@rep:doom3src@repserver:HERMES:8087
CH "/search" DIR#br:/main/scm001;changeset:61@rep:doom3src@repserver:HERMES:8087
CH "/search/search.h" FILE#br:/main/scm001;changeset:61@rep:doom3src@repserver:HERMES:8087

…and that’s good enough for me to build on!

1 Like