Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
David Somers wrote: > Tony Hoyle wrote: >> Nope... if you need an override you need to make your script able to >> handle that somehow. >> >> TBH I normally just temporarily disable them if I need to bypass checks. > > Would be nice to have a flag to disable calling scripts (if only for > debugging purposes!). > > BTW, the situation I was thinking of was that some precommit checks would be > done, and in exceptional circumstances the user would want to force the > commit to happen even though the trigger'd script said abo the commit. > > Somehow I got hit by a bolt of inspiration and think I've found a > workaround.... but, umm... are user variables (-S) accessible by the > trigger scripts ... I couldn't see any sign of them in info_trigger :-( > You can use $VARIABLE on the command line and it'll use user variables if it finds one by that name (or the old cvshome $=VARIABLE should still work). Tony