diegobowen Posted May 3, 2012 Report Share Posted May 3, 2012 hello I have a test instance of Plastic 4 running and I want to create/test some CI trigger for Plastic3.0. Can I use my V4 test instance to create and verify a trigger that I'll use in V3? Link to comment Share on other sites More sharing options...
manu Posted May 3, 2012 Report Share Posted May 3, 2012 Hello Diego, are you talking about checking triggers? Link to comment Share on other sites More sharing options...
diegobowen Posted May 3, 2012 Author Report Share Posted May 3, 2012 Checkin triggers...basically I want to ensure that a user provides check-in comments of a certain length. Thanks Link to comment Share on other sites More sharing options...
manu Posted May 4, 2012 Report Share Posted May 4, 2012 Oh, that's easy! look, you only have to setup a "before-checkin" trigger in your server, for example: cm maketrigger before-checkin “comment required” “ruby c:\triggers\check-comments.rb” And this is a sample that check if a comment is provided in the checkin operation: c = ENV['PLASTIC_COMMENT'] if (c == nil || c == '') then exit(1) end You can tune it to check the comment lenght. The thing I don't understand is this part: Can I use my V4 test instance to create and verify a trigger that I'll use in V3? If you are going to use Plastic SCM 3.0 the trigger must be created in the Plastic SCM 3.0 and if you are going to use Plastic SCM 4.0 you have to create it in the Plastic SCM 4.0 server. There's no communication between 3.0 and 4.0. But if you already have a trigger (the ruby file for example) you can use it in both servers, that's not a problem. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.