Re: Does Jenkins have something like CruiseControl's "ignoreFiles" attribute?

[Chip Whitmer]

We'll look into it. The description sounds like exactly what we need.

 Thanks,
-Chip Whitmer


On Wednesday, June 27, 2012 3:58:20 PM UTC-6, Larry Shatzer, Jr. wrote:
>
> I'm not sure about the TFS plugin, but you could look at  
> https://wiki.jenkins-ci.org/display/JENKINS/Pathignore+Plugin 
>
>

Re: Does Jenkins have something like CruiseControl's "ignoreFiles" attribute?

[Larry Shatzer, Jr.]

I'm not sure about the TFS plugin, but you could look at
https://wiki.jenkins-ci.org/display/JENKINS/Pathignore+Plugin

On Tue, Jun 26, 2012 at 2:37 PM, Chip Whitmer <
cwhit...@servicerepairsolutions.com> wrote:

> CruiseControl's configuration file includes an element 
> with an optional attribute named "ignoreFiles". (See
> http://cruisecontrol.sourceforge.net/main/configxml.html#modificationset)
>
> This allows you to exclude certain files so that changes to those files do
> NOT trigger a new build. For example, if your build process increments a
> counter in a configuration file, you don't want that change to trigger a
> new build -- so you don't get into a loop where each build modifies a file
> which in turn causes a new build.
>
> Is there any way to do this in Jenkins, using the TFS plugin?
>
> -Chip Whitmer
>
>

Does Jenkins have something like CruiseControl's "ignoreFiles" attribute?

[Chip Whitmer]

CruiseControl's configuration file includes an element  
with an optional attribute named "ignoreFiles". (See 
http://cruisecontrol.sourceforge.net/main/configxml.html#modificationset)

This allows you to exclude certain files so that changes to those files do 
NOT trigger a new build. For example, if your build process increments a 
counter in a configuration file, you don't want that change to trigger a 
new build -- so you don't get into a loop where each build modifies a file 
which in turn causes a new build.

Is there any way to do this in Jenkins, using the TFS plugin?

-Chip Whitmer