Open Patrikgrinsvall opened 4 years ago
Hey,
i have the same problem. Run custom build is slow and i have to wait up to 2 minutes.
kind regards Stass
In this case it was the remote webservice that was unstable. Fixing that also fixed the issue.
With unstable you mean not enough performance?if the dialog opens slowsly, then i see no great performance usage of cpu, memory or disc. it is not always the case that the dialog opens slowly. it is so rare that it never really bothered me, but today I looked for a hint or a solution.
I am also seeing this behavior on a configuration with over 90k executions. The long running text file shows that at least some of the running threads are getting hung up looking for changes in an attached VCS root.
The funny thing is, this configuration doesn't have an attached VCS root at all. This issue laid out here may not be the same as I am seeing as the behavior in the web UI observe is the build dialog never opening at all.
Please advise if you'd prefer a new ticket.
Hey. We still have this problem. The dialog for custom builds takes up to 1 minute to open with no clear reason. We have this problem even at night and at this time there is not much work on the server. I will try to reproduce this with new build configurations and with older ones with a few thousands of runs
Sorry guys... I'm not using Teamcity anymore and don't have time to support this project 😕
Best of luck in your future endeavors @grundic - this is still a solid solution to provide dynamic parameterization; thank you for what we have
I see now that there has been some comments on this old issue. So, to clearify, this was not a Teamcity issue. My resolution to the original problem was that the remote machine was hosted on a micro instance on AWS. For some reason, unknown to me, some requests did not get through to the backend.
I have seen the exact same thing in other projects running node.js backends on AWS micro or even small instances behind ELBs, some requests just don't seem to get passed to the backend.
In the browser, this was never an issue, no idea why... Maybe some settings in ELB?
I just wanted to clarify this and not to put any blame on Teamcity.
Any help around this issue would be greatly appreciated!
Around 50% of the times the custom build dialog hangs and after the timeout period and ends up in a broken build dialog. Often it does work as expected, but at what seems to be random it does not work. I'm 100% sure that the web service endpoints is responding since it works in browser, but the request is not received in the webservice when called from within teamcity/ web-parameters.
Screenshot provided.
My custom configuration parameters are:
and environment variables:
In teamcity log directory there is a "threaddumps" directory with logfiles called
2019-10-04_05.10.51-longRequest-11.txt
The logfiles are very long but here the relevant data is below. I don't get any hint from it what can cause the issue. Worth to mention is also that wget to that endpoint from teamcity instance works as expected: