Cruise (from thoughtworks, the authors of CCNet)had an update that said they had better perforce integration. I decide it's time to revisit.
Last visit to cruise, we passed on it. It had nice dependency and build machine farm setups for cascading builds and queueing blocks of commands between machines, but it always did a full 'p4 sync' to a temp client spec, and couldn't use multiple clients from different p4 servers. This was a blocker, because at work, art data and code files live in different repositories. It would also probably eventually clutter p4 metadata beyond belief.
Let's see if things have improved.
Continue reading cruise still frustrating.
