gregsohl Posted April 17, 2012 Report Share Posted April 17, 2012 As we are looking at using PlasticSCM in a fully distributed model, we need some triggers to be in the server environment, particularly on merge operations. I want to so some things with all items as they are merged into the master (remote) repository. What trigger(s) are fired on a sync replication push to the remote repository? I don't see any documented in the triggers documentation that seem appropriate. Developers will never do a "checkin" to the remote repository, only a merge. Are there any other ways to approach this need (for example, logging all file changes upon merge to the remote repository). Thanks. Greg Link to comment Share on other sites More sharing options...
manu Posted April 18, 2012 Report Share Posted April 18, 2012 Hi Greg, I'm not sure about your question, do you mean that you need a trigger that detects merges operations into the master branch and then push this new changes into a replicated server? I think I'm not understanding you :S Link to comment Share on other sites More sharing options...
gregsohl Posted April 18, 2012 Author Report Share Posted April 18, 2012 Developer workflow: Create Task branch from /main in local repository Make code changes Check in code changes to Task branch Merge Task branch to /main in local repository (verify no conflicts with master/remote repository) Use Sync Replication to push /main from local repository to master/remote repository Are there triggers that execute for step 6? These would be needed to start continuous integration processes and to do any other types of notifications I would want. It is this push to /main in the master/remote repository that is the "real" checkin for a fully distributed environment. Greg Link to comment Share on other sites More sharing options...
manu Posted April 19, 2012 Report Share Posted April 19, 2012 Hi Greg, you have the after-checking trigger, you can use it to run only if the commit is in the main branch, if so you can run an "cm replicate" operation and check if the output is a correct replica or it's raising conflicts errors. If the replication operation can be done you are saving the step 6, if not you have to resolve the conflicts. Link to comment Share on other sites More sharing options...
gregsohl Posted April 19, 2012 Author Report Share Posted April 19, 2012 Manuel, The trigger needs to run on the server housing the master repository. That's what's important - the master copy of the source. Nothing is "final" until it gets there. There is no checkin operation as far as I know after sync replication push local-to-master, or am I missing something? Greg Link to comment Share on other sites More sharing options...
manu Posted April 20, 2012 Report Share Posted April 20, 2012 No no, there's no checkin operation after the replication. I was speaking about the point 4, after committing the merge in the main branch, just before the replication. Link to comment Share on other sites More sharing options...
gregsohl Posted April 20, 2012 Author Report Share Posted April 20, 2012 Manuel, please answer this question: Are there triggers for after sync replication? If not, how can I get notified of a "push" to the master repository? Thanks. Greg Link to comment Share on other sites More sharing options...
manu Posted April 20, 2012 Report Share Posted April 20, 2012 Nop, there are no after-sync triggers. As there are no triggers, all goes by an external application monitoring for new changesets. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.