Issue triggering a build from VCS Roots

I recently switched VCS from Visual Source Safe to Team Foundation Server and I am now having issues with a Build Configuration triggering a Build when changes to the VCS Root are detected.

I have multiple Build Configurations, and this is the only one that does not seem to be working. I have messed with the VCS Trigger rules (originally empty) to include +:. with no luck. And then I copied the Rules from another Build Configuration's VCS Trigger, also with no luck.

The files are being detected by TeamCity (i.e. they show up as Pending), but a Build is never added.

Attached are my current VCS Trigger settings. There are 4 VCS Roots attached to this build configuration, and none of them will trigger a build.

Any ideas what's going on?

Thanks,
~Alex

P.S. I am using TeamCity v7.0.4



Attachment(s):
Report VCS Trigger.png
7 comments
Comment actions Permalink

Hi,

Could you please provide us with teamcity-server.log and teamcity-vcs.log logs while commit a change and wait for the build not starting for several time.

0
Comment actions Permalink

I was out sick yesterday. When I came into work today, there was a build in the queue for this project. I let it build, and then shut down the TeamCity server, cleared the log folder, and started the TeamCity server again. I committed a change to one of the VCS roots and it was detected fairly quickly. Then I waited about 10-15 minutes without a build being added to the queue. I then committed a file in a different VCS root. About 5 minutes later, there is a build in the queue, but there is still only 1 pending item (i.e. the second commit has not been detected). Just now (probably about 10 minutes after commit) the second change has been detected as pending.

Attached are the log files you requested for these actions.

Thanks,
~Alex



Attachment(s):
teamcity-logs.zip
0
Comment actions Permalink

Could you please also collect temcity-server.log in debug-general mode (it can be turned on in Administration | Diagnostics | Troubleshooting) while reproducing the issue?

0
Comment actions Permalink

I shut down the server and cleaned out the log files, then started the server again. I then placed it in debug-all mode (missed the part where you said debug-general). I committed the file to one of the VCS Roots for this build configuration and it showed up as Pending. I then realized you wanted it in debug-general, so I switched to that debug mode. Attached is the log file for these actions.

2014-06-02 09:18:42,319 is when I switched to debug-all
2014-06-02 09:25:34,612 looks like when the commit was detected.
2014-06-02 09:31:50,635 is when I switched to debug-general

Thanks,
~Alex

P.S. If this works like it did on Friday, then eventually it will trigger the build (a commit in the morning didn't trigger until 3-4 PM). If it does, I'll also attach the log file at that time.

EDIT: Added the timestamp for when the commit was detected.

Message was edited by: Alex Yeisley



Attachment(s):
teamcity-server.log.zip
0
Comment actions Permalink

Thank you for logs. From logs we see that the build configuration "EDB 4.3.3 :: EDB Report Files" should be started, is it correct? Can you please doublecheck that Trigger is configured for exactly this build configuration.
We also recommend you to upgrade to new TC version, if it is possible. There were lots of fixes done in new version, also it will be easier for us to investigate the issue and to fix it.

0
Comment actions Permalink

I don't know what you mean when you say the build configuration "should be started." At the time the log was from, the changes to the VCS root were detected and show up as Pending changes for the "EDB 4.3.3::EDB Report Files" Build Configuration. Attached is a screenshot of the Build Trigger for that Build Configuration.

Additionally, while I was at lunch, a build did seem to finally trigger. Attached is the log (which includes all of the previously uploaded log as well).

2014-06-02 12:03:53,890 is when the Build appears to have triggered into the Queue.

Thanks,
~Alex

P.S. I do not think we can upgrade to the new version of TeamCity at this time. TeamCity has been working fine for us, until we needed to move from VSS to TFS. I will keep that option in mind though.



Attachment(s):
teamcity-server - Build Triggered.log.zip
TeamCity Build Trigger issue.png
0
Comment actions Permalink

Thank you for logs. We could not find the reason of the issue from logs. We've tried to reproduce this issue in new version, but we could not. The previous versions have limited support. So please upgrade to 8.1.x TC version and inform us if the issue is reproduced.

0

Please sign in to leave a comment.