TeamCity Cloud logs
Hi! We are considering moving from TC on-prem to TC Cloud and im having this issue: vsc build triggers are kinda slow - 10-20 s delay. Maybe i configured webhooks wrong maybe something else.
So i was wondering where can i see logs of server like those on premises in Administration - Server Administration - Diagnostics so that i can see trigger logs vcs logs etc.
Please sign in to leave a comment.
Please let me know your TeamCity Cloud instance URL, and I will look into the issue you describe.
Best regards,
Anton
Good day! build.teamcity.com.
You have multiple VCS roots with active commit hooks. Could you let me know which build configuration you experienced this issue with, and also at what time? It will narrow the search significantly.
Best regards,
Anton
test-cameras-build 5 min ago. Now as i can see git did a push at 18:26:53 (local time here). Also got response from server. And server started build at 18:27:05.
I checked the logs and didn't see any significant issues with it. With commit hooks, the process is as follows:
1. User pushes
2. GitHub receives the data
3. GitHub triggers a hook that notifies TeamCity
4. TeamCity checks with GitHub what has changed
5. The VCS trigger happens
6. The trigger process puts the build in the queue
7. The build starts
In your case, the hook was received at 14:26:53, and the check for changes was scheduled. The collection of the changes started at 14:26:54. At 14:27:00 the changes were collected, and at 14:27:05 the build was triggered, put in the queue and started almost immediately.
The only problem I see is between 14:27:00 and 14:27:05. There was an additional revision calculation at that time with the following warning (I masked the VCS root name):
```
[2024-05-27 14:27:00,918] WARN [ical executor 4] - CS.CommitHooks.WebHooksManager - Hook HookInfo(url='https://api.github.com/repos/<U***>/<VCS Root>/hooks/480165962', callbackUrl='https://build.teamcity.com/app/hooks/github/1fa352ff-333e-4664-b2b5-e3615746cd8c', status=OK, lastUsed=Mon May 27 14:26:53 UTC 2024) have no revision saved for branch refs/pull/32/head, but it should be 9ee2770da5f88abb4aa1f2f5b20e35929fca62e8
```
I hope it is helpful.
Best regards,
Anton
Got it. Thank you! So basically everything was going as planned just time to execute internal tasks? Good. Now by any chance can I get access to logs not contacting support? Like mb api call or something? Too used to on-prem edition and that would save time both for us and for you. Thanks again for resolving issue with trigger
I got a confirmation that we don’t have any way to provide access to the logs for the users, and for now there are no plans to provide such access. Thank you for your understanding.
Best regards,
Anton