ccnet plugin exclusion filters

[malcolmstorm]

we have just updated our build server to Vault 4.1.3 and have attempted to use the new ccnet plugin for Vault 4.1.3. The orginal source control block was:

<sourcecontrol type='filtered'>
<sourceControlProvider type='vault' autoGetSource="true" applyLabel='false'>

<folder>$/Projects/Abc/Mainline</folder>
<workingDirectory>.</workingDirectory>
<host>HostName</host>
<repository>RepName</repository>
<ssl>false</ssl>
<useWorkingDirectory>false</useWorkingDirectory>
<cleanCopy>true</cleanCopy>
<executable>c:\program files (x86)\sourcegear\vault client\vault.exe</executable>
</sourceControlProvider>

<exclusionFilters>
<pathFilter>
<pattern>s**/TrainingFund.AssemblyInfo.cs</pattern>
</pathFilter>
</exclusionFilters>
</sourcecontrol>

this is because a successful build updates and checks backin the assemblyinfo file.

Now that I have replaced the "Vault" type to "VaultPlugin" the build gets into an endless loop of building. Is the filtered source control supported? Are labels still automatically excluded? Or has the path name somehow changed?

[malcolmstorm]

Sorry the last part of the config should read of course:

<pathFilter>
<pattern>**/Abc.AssemblyInfo.cs</pattern>
</pathFilter>

[shannon]

We've had one other report of this and we're investigating the cause. Yes, filtering should still be supported.

(Item:13721)

[avonwyss]

Issue still seems to be the same in V4.1.4... it would be great to have this one fixed soon!

[lbauer]

Thanks for the update. I have updated the bug with your comments.