RE: [Ccnet-user] Vault Obliterate triggered build

[Ian O. <ia...@so...>]

Perry,

I'm of the opinion that a hard-coded filter makes sense, but I believe =
an ActionFilter will work in the mean time.  (Can anybody make a case =
for actually wanting to trigger a build when something has been =
obliterated?  I can't imagine why.)

Andy,

If you're not familiar with ActionFilters (I wasn't), the documentation =
is here: =
http://confluence.public.thoughtworks.org/display/CCNET/Filtered+Source+C=
ontrol+Block#FilteredSourceControlBlock-ActionFilter.

I haven't actually tested it, but a quick look at the code makes it look =
like obliterate will be correctly parsed from history, and you could =
filter out the "Obliterated" action to prevent a build from being =
triggered.

--
Ian=20

=20


________________________________

	From: ccn...@li... =
[mailto:ccn...@li...] On Behalf Of Perry =
Ismangil
	Sent: Wednesday, February 22, 2006 10:58 AM
	To: ccn...@li...
	Subject: Re: [Ccnet-user] Vault Obliterate triggered build
=09
=09
	On 2/22/06, Ian Olsen <ia...@so...> wrote:=20
=09
		Andy,
	=09
		This certainly doesn't sound like correct behavior from a build =
standpoint, but it does make sense that it happens.  Obliterate does =
produce a history event and a new folder version, and we're not doing =
anything to filter these out, so a build would be triggered.  I've added =
it as a CC.NET bug and I'll see what I can do to fix it.
	=09
	=09


	Can we hardcode a filter for Obliterate in the Vault cc.net provider?=20
=09
	In the short term, can we use ActionFilter to filter it out? Does it =
even translate to an action?=20
=09
	--=20
	Perry Ismangil=20