Lumz

Nevermind. The solution is the same as the changed files from the merge are in the stdin.

Hi, I'm trying to figure out what would the destination workspace be in a specific case of merge inside a before-clientcheckin trigger. When I have local changes I can use stdin to find changed files and use cm status on the right workspace but when I have pending merge links (PLASTIC_PENDING_MERGE_LINKS) and no input in stdin (no local changes) I cannot think of a way that gives me the destination workspace. It has to be a before-clientcheckin. Any ideas ? Regards.

Hi, I've been trying to install a before-clientcheckin trigger and successfully did so until I added a couple of lines to my .bat file. Since I've added a msbuild.exe command to the script the cm ci command is just hanging forever. So is the GUI if I try to checkin from there. The .bat file is running fine from cmd.exe. I also tried to read the log after setting the .conf file and it seems to get stuck on a cryptic: 2016-12-05 13:56:39,639 DEBUG Channel - Purging connection to plastic://pickledwarf-pc:8087/BranchHandler 2016-12-05 13:56:39,639 DEBUG Channel - Purging connection to plastic://pickledwarf-pc:8087/RepositoryHandler 2016-12-05 13:56:39,639 DEBUG Channel - Purging connection to plastic://pickledwarf-pc:8087/TriggerHandler Anyone knows what this is about ?