Ignoring files for build triggering Follow
My build automatically checks some jar files into perforce that are needed by other products. I am trying to ignore these files for build triggering, so the build won't kick off continuously. The jar files are automatically sync'd during build time. For example, //shared/71/centralconfigurator/bpo-config.jar is sync'd to ${build.working.dir}/Hoth/shared/71/centralconfigurator, modified by the build and checked back in.
What is the correct syntax for the "Do not trigger build if all changed file names match any of the following wildcards:" text box? I have used many combinations, such as the following without success.
bpo-config.jar
shared/71/centralconfigurator/*.jar
Hoth/shared/71/centralconfigurator/*.jar
Thanks, Linda
I meant to mark this as a question. I am using TeamCity Version 2.1.1(build 4261).
Message was edited by:
Linda Springsteen
Please sign in to leave a comment.
I would like to know this too.
Please provide examples!
I tried
mydir/*/.*
-> did not work
I use Perforce as my SCM. Using the full depot path
with wildcards seems to work for me.
e.g.: //shared/71/*/.jar
Hope that helps.
-Dave
do you mean like d:/work/project/mydir/*/.* on windows?
Tried
*/mydir//.*
that also did not work.
Could someone from Jetbrains help please?
I'm wasting a lot of time with trial and error now...
found that
*.bat
*.txt
does work.
I wonder if it will work with slashes too? (so that you could exclude specific directories rather then specific extensions?)
I mean file location in source control as opposed to your sandbox.
So, in Perforce, an example of where a file would be in source:
//depot//lib/main/my.jar
even though the local sandbox file location might be, for example:
D:/work/project/lib/my.jar
It's the source location you would use as a filter.
-Dave
That seemed to work. Thanks, Linda
Hello Linda,
ignoring files can be described with their repository name (specific for
each version control) and '*' and '?' in their paths (see
http://www.jetbrains.net/confluence/display/TCD/VCS+Triggers).
The important question is about file name using for checking.
For perforce repository file name is depot name,
for svn - its svn url,
for cvs - relative path.
We will change it in the next TC version (benaris), the path using here will
be uniform for all version control supports.
Sorry for delay with the answer.
--
Olesya Smirnova
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
"Linda Springsteen" <linda.springsteen@webmethods.com> wrote in message
news:17468839.1184703446637.JavaMail.itn@is.intellij.net...
>
>
>