James Helm

Created August 23, 2019 21:58

Thanks.  I like 'Pending' as well, until it's wrong.  We just work with building specific tags/branches quite bit so the 'Pending' and change list can be quite wrong for many of our builds.  I don'...

1. Community
2. TeamCity General Topics
3. TeamCity 2019.1.2 - VCS Trigger Rules not working - How can I prevent a build from starting by blocking specific directories?

• 0 votes

Created August 23, 2019 15:58

I just commented about 'Pending' changes in another thread.  We do something similar where we have our builds pointed at our 'Trunk', which rapidly collects changes.  Many times we'll point that bu...

1. Community
2. TeamCity General Topics
3. Reset pending changes when using tags as "branches"

• 0 votes

Created August 23, 2019 15:55

Thanks for the reply Denis, I appreciate it. I'm at the point where I've configured it so that it DOES NOT trigger a build when the changes happen in that directory, but it does still show the item...

1. Community
2. TeamCity General Topics
3. TeamCity 2019.1.2 - VCS Trigger Rules not working - How can I prevent a build from starting by blocking specific directories?

• 0 votes

Created August 09, 2019 19:24

One more question.  I think I was able to get this to work.  Looking at the VCS Checkout rules above, for rule #3, I added two VCS Trigger rules to see if they would work: -:Dep_Tools/**-:Dep_Tools...

1. Community
2. TeamCity General Topics
3. TeamCity 2019.1.2 - VCS Trigger Rules not working - How can I prevent a build from starting by blocking specific directories?

• 0 votes

Created August 09, 2019 17:43

Would it be possible for somebody internal to JetBrains to set this up and see if it's working as expected? It's basically one VCS Root (Subversion) with two Checkout rules.  It syncs one folder & ...

1. Community
2. TeamCity General Topics
3. TeamCity 2019.1.2 - VCS Trigger Rules not working - How can I prevent a build from starting by blocking specific directories?

• 0 votes

Created August 09, 2019 17:40

If I read what you wrote correct, you are saying it first applies the VCS Checkout rules, which includes the 'Build' folder, and then checks the VCS Trigger rules?  If that is the case that it seem...

1. Community
2. TeamCity General Topics
3. TeamCity 2019.1.2 - VCS Trigger Rules not working - How can I prevent a build from starting by blocking specific directories?

• 0 votes

Created August 09, 2019 16:45

Is this an issue where the VCS Trigger rules don't override the VCS Checkout rules?  I've tried some more things but no matter how I format the VCS Trigger rule syntax the build always starts. Jim

1. Community
2. TeamCity General Topics
3. TeamCity 2019.1.2 - VCS Trigger Rules not working - How can I prevent a build from starting by blocking specific directories?

• 0 votes

Created June 19, 2019 16:38

So, it seems this error went away when I restarted the server.  I guess there's nothing more I need to do.

1. Community
2. TeamCity General Topics
3. Build 2019.1 - How can I fix the "Could not fix location of build artifacts directory" error?

• 0 votes

Created June 18, 2019 16:12

I see.  And the bug is that instead of the limited UI with ONLY the 'prompt' parameters, it's instead showing the full list of parameters.  Is that correct?

1. Community
2. TeamCity General Topics
3. 2019.1 - 'New' UI vs. 'Classic' UI's 'Run' button issue

• 0 votes

Created June 18, 2019 14:51

The first one does not have any of those, only the 2nd.  On our main build server, which has 54 build configurations, none of them use the 'prompt' parameters.  We do that on our other two servers....

1. Community
2. TeamCity General Topics
3. 2019.1 - 'New' UI vs. 'Classic' UI's 'Run' button issue

• 0 votes