I have a question about perhaps best practices in integrating Swarm, Perforce and Git Fusion. I have a Perforce server and a Swarm. I'm trying to integrate Git Fusion into this picture. Now the Swarm server serves the Swarm web app as well as kicks off workers via the cron job. One thing I discovered was that I had a copy of the swarm-trigger.sh put over on the Perforce server. Then some time later I updated Swarm to 2015.1/1060524 from 2014.3/897280. Today I compared the swarm-trigger.sh script on the Swarm server with the copy that I had put on the Perforce server and noticed the obvious problem - my swarm-trigger.sh script on the Perforce server is old. Now I can easily copy the new one over but I was wondering what would be a best practice here? Should I simply install Swarm on the Perforce server? I'm not sure I want the added burden of serving the Swarm web site from there. And where should that little cron thing run from?
As for Git Fusion, the install doc says:
you should exclude the user git-fusion-user from triggers on change-submit, change-commit, and change-content because they may block Git Fusion's operation.
I assume that this would only be an issue for Perforce repos that communicate and/or correspond to Git Fusion git repos of some sort. Therefore I'm concerned about "global triggers" or triggers set to the path of //... There is one swarm-trigger.sh line with //... in it and that's:
swarm.commit change-commit //... "/path/to/triggers/swarm-trigger.sh -t commit -v %change%"
Should I be concerned that this trigger may block Git Fusion?