Home
TeamCity Support | JetBrains
Contact Support
Community
Sign in
James Helm
Total activity
52
Last activity
May 25, 2021 01:35
Member since
May 29, 2019 18:44
Following
0 users
Followed by
0 users
Votes
0
Subscriptions
8
Activity overview
Posts (7)
Comments (37)
Sort by recent activity
Recent activity
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...
Community
TeamCity General Topics
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 & ...
Community
TeamCity General Topics
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...
Community
TeamCity General Topics
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
Community
TeamCity General Topics
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.
Community
TeamCity General Topics
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?
Community
TeamCity General Topics
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....
Community
TeamCity General Topics
2019.1 - 'New' UI vs. 'Classic' UI's 'Run' button issue
0 votes
Created
June 17, 2019 20:50
The configurations aren't 'exactly' the same for the two build configurations. One of our servers shows the proper 'Run' button with the 'New' UI, for ALL of its build configurations, and another ...
Community
TeamCity General Topics
2019.1 - 'New' UI vs. 'Classic' UI's 'Run' button issue
0 votes
Created
June 14, 2019 16:00
I think I may have confused the issue by referring to our servers as 'newer' and 'older'. All three of our TeamCity servers are running build 2019.1. Using the 'New experimental UI' on all of them...
Community
TeamCity General Topics
2019.1 - 'New' UI vs. 'Classic' UI's 'Run' button issue
0 votes
Created
June 14, 2019 14:58
On the 'newer' servers, all the build projects contain 'Prompt' parameters, but only the 'Run...' button is shown on the 'New' UI. On the older server, we have a ton of projects, none of which hav...
Community
TeamCity General Topics
2019.1 - 'New' UI vs. 'Classic' UI's 'Run' button issue
0 votes
«
First
‹
Previous
Next
›
Last
»