Any ideas on this guys!

My management is after me on this. Please help...

--Nikhil

On Feb 26, 2:29 pm, maverick80 <[email protected]> wrote:
> i'm having a bit of probelm understanding the filtered source control
> for SVN. Here is the block from my ccnet.config:
>
> <sourcecontrol type="filtered">
>                 <sourceControlProvider type="svn">
>                         
> <trunkUrl>http://svnserver:81/svn/suncity/source/branches/author</
> trunkUrl>
>                         <workingDirectory>G:\Suncity\Source\branches\author</
> workingDirectory>
>                         <username>usr</username>
>                         <password>pwd</password>
>                         <timeout units="seconds">3600</timeout>
>                 </sourceControlProvider>
>                 <inclusionFilters>
>                         <pathFilter>
>                                 
> <pattern>/suncity/source/branches/author/**/*.*</pattern>
>                         </pathFilter>
>                 </inclusionFilters>
>                 <exclusionFilters>
>                 <pathFilter>
>                         
> <pattern>/suncity/source/branches/author/build/scripts/
> version.txt</pattern>
>                 </pathFilter>
>                 </exclusionFilters>
>         </sourcecontrol>
>
> The purpose was to exclude version.txt to trigger the build. Any other
> check-ins should trigger. Now, it is not triggering the builds for any
> check-in.
>
> I suspect this is to with the <inclusionFilters> I'm using. Could
> someone guide me on this?
>
> Regards,
> Nikhil
> On Feb 4, 12:51 pm, Nikhil <[email protected]> wrote:
>
> > Thanks Ruben...
>
> > On Feb 4, 12:47 pm, Ruben Willems <[email protected]> wrote:
>
> > > Hi
>
> > > take a look at the filtered source control 
> > > blockhttp://confluence.public.thoughtworks.org/display/CCNET/Filtered+Sour...
>
> > > this should cover it
>
> > > with kind regards
> > > Ruben Willems
>
> > > On Wed, Feb 4, 2009 at 8:44 AM, Nikhil <[email protected]> wrote:
>
> > > > We check-in the version number of each build in a file.
>
> > > > Now there are times when no check-in happens on a day apart from the
> > > > version file (checked in after the daily build). CCNET takes the
> > > > version file commit as a modification the next day and triggers the
> > > > build.
>
> > > > I want to curb this and do not want a build in case there are no check-
> > > > ins other than version file. Is there a way to get this done inside
> > > > CCNET?
>
> > > > If I can exclude the file from getting updated daily or just check
> > > > that this is the only update and ask CCNET to not trigger the build
> > > > today?

Reply via email to