LoganBarnettASU

My workaround for the time being is to place the Ruby file in a root directory (/foo/bar.rb or c:\foo\bar.rb), and then the trigger looks like this: cm maketrigger after-update "after update" "ruby /foo/bar.rb" That seems to work for us. It's actually kind of nice in that we don't have to configure this trigger for each machine. The only drawback is that we need root/admin access, but we were able to work around that with sudo and running as administrator on Windows.

I tried making the trigger locally (whereas I was making it on the server before). This resulted in the same behavior (runs on all systems). Here's my maketrigger command: cm maketrigger after-update "Update art on update (root)" "ruby /.arx-plastic/update_art.rb" Are there any switches I can pass that would make it work for just me?

Manu, I don't believe we're using shared workspaces. I've created a new workspace under a different user for each machine we have Plastic installed on. I assume that the owner of the trigger (in this case it's me) should be the only user the trigger is fired against. In our case this one trigger is firing against every user on different machines. Perhaps this is the real problem? I thought this behavior was to prevent us from having to write a trigger a bunch of times, but in light of this path issue, I'd say making independent triggers makes more sense. -Logan

Hello, My team is working in a mixed OS X and Windows environment. We want the triggers we make to work on both systems, but I suspect our problem is that the paths we're using aren't valid for both operating systems. $ cm listtriggers 2 Update art on update ruby /Users/atlantisremixed/.arx-plastic/update_art.rb LoganBarnett after-update The Ruby script we're running works great for both OS X and Windows when running standalone, but that path won't work for WIndows in the trigger so it doesn't even get to the Ruby script. What can I do to make my trigger platform agnostic? All of the examples in the PDF seem to prefer one platform or another, but never something universal. It would be nice if I could just do ~ for a home directory but I don't think that expands correctly. Perhaps I was doing that wrong? Thanks in advance! -Logan