exclusionFilters not working in CruiseControl.NET

[davenovak]

Hello --

I am using the latest version of Vault (4.1.4) and the most recent Vault Plug-in for CruiseControl.NET (also 4.1.4). I have yet to get my exclusionFilters to work properly using the plug-in. They are blissfully being ignored. Here's an example:

Code: Select all

<project name="MyProject 9.0.0 Client">
    <triggers>
        <intervalTrigger buildCondition="IfModificationExists" seconds="30"/>
    </triggers>
    <sourcecontrol type="filtered">
        <sourceControlProvider type="vaultplugin" autoGetSource="true" applyLabel="false" cleanCopy="false">
                <username>*****</username>
                <password>*****</password>
                <host>vault.ddcinternal.com</host>
                <repository>Development</repository>
                <folder>$/MyProject 9.0.0/Client</folder>
                <setFileTime>modification</setFileTime>
        </sourceControlProvider>
        <exclusionFilters>
            <pathFilter>
                <pattern>Client/Flash/**/*</pattern>
            </pathFilter>
        </exclusionFilters>
    </sourcecontrol>
</project>

I'm fairly convinced that this is a bug in the plug-in since this exact same project block works correctly when using command-line Vault (i.e., type="vault"). The only problem with command-line Vault, however, is that it is very slow (since it has to log in/out with each command).

I really would like to see this problem fixed ASAP. From what I saw in a prior post (http://support.sourcegear.com/viewtopic ... 44&p=46798), I'm not the only one having an issue. Any solution or workaround would be greatly appreciated.

Thanks,

--Dave Novak

[shannon]

I don't have a workaround to give you other than using the old plugin, but I've bumped the priority and we'll get it looked at soon.

13721

[davenovak]

While you-all are looking into this, you might want to take a close look at inclusionFilters as well. I was having a problem with that too but worked around it by updating my <folder> specification to start at the desired root. As a result, I do not specify any inclusionFilters.

On behalf of CruiseControl users everywhere, I hope this issue is resolved quickly.

Thanks,

--Dave Novak

[shannon]

It wouldn't surprise me for those two to be related. Thanks for the extra heads up, I'll make sure we look into both.