Remote Run Pre-Tested Commit Debugging
I am having an issue doing a Pre-Tested commit with TeamCities Visual Studio Plugin. The build runs fine but for some reason the commit doesn't occur. Are there log files anywhere that might give an indication as to why the commit didin't happen? We are using Peforce as our SCC.
Please sign in to leave a comment.
Hello, Patrick.
Is it isolated case? What build do you use?
Yep, you could find our logs in %UserAppData%/Local/Temp/JetLogs directory.
This is an issolated case, it doesn't happen every time which is why I wanted to know where to go look to try and debug it. I looked in the %UserAppData%/Local/Temp/JetLogs logs to see if I could find any information about what could cause the submit to fail, and I didn't see any information related to what perforce commands the tool was trying to execute, so I couldn't tell where things might have gone wrong. I was hoping there might be another place where that information was being captured.
In case of any errors when interacting with Perforce (or any other VCS), personal change changes it status on MyChanges view to "Commit failed" and information about error is accessible throught "Show commit failure reason" action, placed on toolbar and context menu.
If your change has no status at MyChanges view, this suggests that we clear information about your commit before your personal build was finished, so delayed commit wasn't started, and you have no Perforce related messages in logs.
I create an issue in our tracker for this problem. http://jetbrains.net/tracker/issue/TW-9438
How do I go about determining what caused that scenario?
Do you closed Visual studio during Teamcity running your personal build?
In this case, Visual Studio was not closed. We learned the hard way that things don't get submitted if you close Visual Studio before the operation completes. In this case, the build completes with green check boxes, but nothing is submitted.
Did your personal build was finished pretty quick (less than a minute)?
No, it took the regular time and log on the server shows it ran all the tests associated with the configuraiton.