Hi Jeff, Generally speaking, an access control policy would be a good thing.
http://bugzilla.mkgnu.net/show_bug.cgi?id=859 On Mon, 2010-09-20 at 16:09 -0700, Jeff Leyser wrote: > We want SCMBug (Subversion + Bugzilla) to always require a bug ID on > checkin. But if the devs give a certain ID (say, 99), and *ONLY* that > ID, the integration should abort and not update anything. ... but yes, you should be able to make the determination that you don't want to commit to begin with, and not issue the commit statement. > Where in the integration would be the best place to put that check? > And how best to 'exit out' of the integration leaving everything as > it was? You should add this change in Glue.pm:check_policies. You should be able to follow the example there on how to check an $activity, and how to exit with a log_fatal_error.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
