Hi Ross,
Thank you very much for the prompt reply. Well I did come across this
document and in fact I am currently using the exclusionFilters but I
was under the impression that the later was used to prevent builds
taking place. Whereas what I am trying to achieve is to prevent
copying the *.vsssscc, and the *.scc files into the published folder.
Have I missed something? If so kindly, provide some insight after
reviewing the following source control configuration:
<sourcecontrol type="filtered">
<exclusionFilters>
<pathFilter>
<pattern>**/*.vssscc</pattern>
</pathFilter>
</exclusionFilters>
<inclusionFilters />
<sourceControlProvider type="multi">
<requireChangesFromAll>False</requireChangesFromAll>
<sourceControls>
<vss>
<project>$/Folder/Project</project>
<username>******</username>
<password>*******</password>
<executable>C:\Program Files\Microsoft Visual Studio\VSS
\win32\SS.EXE</executable>
<ssdir>\\server\repos</ssdir>
<autoGetSource>True</autoGetSource>
<applyLabel>False</applyLabel>
<workingDirectory>C:\CruiseControl\Builds\Project</
workingDirectory>
<culture>en-US</culture>
</vss>
</sourceControls>
</sourceControlProvider>
</sourcecontrol>
Thank you very much for any help. :-)
Jacques
On 25 août, 15:54, "Ross Patterson" <[EMAIL PROTECTED]> wrote:
> On Mon, Aug 25, 2008 at 15:34, [EMAIL PROTECTED] <
>
> [EMAIL PROTECTED]> wrote:
> > Sort of filter so to speak. How can I do that?
>
> Funny you should call it that - that's what it's called. Check out the
> documentaiton for Filtered Source Control
> athttp://your_CCNET_server/ccnet/doc/CCNET/Filtered%20Source%20Control%...
> .
>
> Ross
