flynn@informz Posted July 3, 2014 Report Share Posted July 3, 2014 We are currently trying to create a before-checkin trigger so that all checkins are required to be linked to an issue with our issue tracking system, VersionOne. Since this linking is just an attribute, our thought was to check to see if an attribute for VersionOne had been added to the changeset but we are not seeing anything in the available data to enforce that. The documentation for triggers also seems a little out of date. Any suggestions or thoughts would be extremely helpful Link to comment Share on other sites More sharing options...
manu Posted July 4, 2014 Report Share Posted July 4, 2014 Hi Flynn, Ummm I see a problem here, you can't set an attribute for a non existing changeset.... You need to create it first... Maybe you can use the changeset comment to force developers to write the VersionOne issue id with a well known prefix. Then with the after-ci trigger create the attribute programatically, if the developer forgets to write the ID you can throw an error to notify it to the developer. Do you use the serial development methodology (everybody at main) or branch-per-task? If it's the second one it's much easier due to you can bind the branch with a versionone issue and deny all the commits (with a before-ci trigger) until the branch attribute is set. BTW, did you test the VersionOne "Task on changeset" working mode? http://plasticscm.com/documentation/extensions/plastic-scm-version-control-task-and-issue-tracking-guide.shtml#Chapter8:VersionOneintegration Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.