Jump to content

Conditionally running a checkin trigger?


cnolanASU

Recommended Posts

Hi,

We are trying to execute a trigger after-clientcheckin, but only when certain repositories are checked in. The information supplied to standard input doesn't include any repository id, so we don't have a way to determine where it's from short of parsing the checkin pathnames (which may not be the same on everyone's computer).

What's the best way to go about this?

Link to comment
Share on other sites

You're right. We're not adding this information right now to the trigger output. :o

The only thing you can do is to run a "cm ls" on the paths you're interested on and list its repository.

We'll add info about the repo ASAP.

Please do not forget to submit your request to our "uservoice" site... it is a great improvement suggestion!

Thanks

Link to comment
Share on other sites

Thanks for adding the request, remember that the "cm ls" has a powerful output format.

Just issue cm ls --help to review all of them, 22 in the last release.

The output parameters of this command are the following:

size 0

date 1

type 2

location 3 prints br:branch#cset

checkout 4

co 4

name 5

changeset 6

cset 6

fullpath 7

path 7

repspec 8

owner 9

formattedsize 10

revid 11

parentrevid 12

itemid 13

brid 14

repid 15

server 16

symlinktarget 17

hash 18

chmod 19

wkpath 20 prints path relative to workspace root

branch 21

newlocation 22 prints cset@branch

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...