G'day Jeff,
The access control that Kristis referenced would certainly be a good
thing (in fact, I'd really really like it!). In your particular case,
though, if you have already configured scmbug to only permit users to
commit against bugs that are assigned to them, perhaps you could simply
create a dummy account in Bugzilla, assign a bug to it, and then use
that bug's ID as your "certain ID"? I guess this only works if the
"certain ID" doesn't have to be memorable like "99" (or if you're
currently up to bug #98!).
Regards,
David
[Kristis, in case you saw the bounce, I fixed up my email address myself
this time :) ]
________________________________
From: [email protected]
[mailto:[email protected]] On Behalf Of Jeff Leyser
Sent: Tuesday, 21 September 2010 8:39 AM
To: [email protected]
Subject: [scmbug-users] Special Case a Specific Bug ID
Hi,
I realize as I ask this it is ill-advised, and a hack, and a
poor workaround. But my Devs are insistent.
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.
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?
Not looking for the complete patch here, just some guidance on
where in the code I should start.
Thanks,
Jeff
----------------------------------------------
David O'Shea
Senior Engineer
EMS SATCOM Pacific Pty Ltd.
[email protected]
www.emsglobaltracking.com
T: +61 8 8260 8187
_______________________________________________
scmbug-users mailing list
[email protected]
http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
