guys.
I'm having some trouble with TeamCity build agents.
I have an agent i'm using for calabash automation. When i'm running the build i'm getting :
Agent didn't come for the command in a 30 seconds.
I can see my agent in "Connected agents" tab, and "Disconnected" tab, and builds are not running. I tried to reboot the machine several times, and restarting the agent daemon on that machine, nothing happens, even when I shut down the machine it's still in "connected" and "disconnected" tabs.
There was a bug in TeamCity 9.1.x which is fixed in 9.1.4 which may cause such problem. You could use workaround from issue comments.
Related
I have a Windows 10 Pro VM, that I want to run a Localhost Katalon Agent on.
I have it running successfully, but I would like for it to start when the computer starts.
Right now, I have it running by putting a Shortcut in the Startup folder. But this only gets triggered if someone logs into the machine.
How do I get the Agent to start when windows startup, even if no one logs in?
Come to find out. the Katalon Agent comes with NSSM. I was able to use that to create a Service using these instructions: https://stackoverflow.com/a/26626771/4739712
We have a testing framework made in AutoIt for our Windows apps (older legacy apps that we will continue supporting). These have never been run on a schedule or part of CI (always been run manually). I tried to get some kind of auto run (or even just status reporting) out of the tests, with minimal luck.
I have a VM where the tests can run. I experimented with my own web app, which works okay locally for running and status reporting. But when set up on the server, AutoIt reports it cannot open the application. Same thing happens if I try to run the tests from a .bat file.
My current solution is to have AutoIt call my web app to report status (working okay locally, untested on the server), or to see if I can get AutoIt to report results back to TeamCity. I have the agent installed but when I run the build from TeamCity, AutoIt reports it can't launch the application. I tried this while logged into the VM, logged out, with RDS open; no luck.
Is it possible to run the tests manually from the VM and send results back to TeamCity? When I run them from TeamCity it reads the AutoIt output (which is in the expected format), but I need to let TeamCity know to update the results (so we can use TeamCity rather than my web app to show the results).
I may need to find a way to let TeamCity know a build has been started, which might then let it know to keep an eye on the process' output, but I'm not positive. Any ideas?
I solved this so it could be done more traditionally.
If anyone is confused by what "running the agent from the console" meant, it just means installing the agent without selecting the "as a service" checkbox, and then manually starting the agent by cd'ing to the BuildAgent/bin directory and running the command agent start. I also created a batch file that will do this automatically (but you must run it as admin).
Further, I found AutoIt couldn't do anything if the test doesn't run from the right directory, so I had to devise a solution to this.
The only issue now is that I have to have an old laptop always connected to the virtual machine the tests and app run on (since the AutoIt tests won't work without the VM desktop being interactive).
I've a Windows Server 2012 R2 based Hyper-V Host, which contains a Windows Server 2012 R2 VM as a VPN using RRAS and another VM running Debian plus the Jenkins (latest version) master server. Using this VPN, a private hosted Windows Server 2012 R2 VM act as Jenkins slave using those VPN connection. For better distinction, call this one node1.
This is bascially working as expected, but there is a problem: Sometimes, when I start a buildjob on node1, it hangs. Only the first 2 steps (Started through user XYZ and Build on slave node1 in workspace C:\jenkins are shown in the log, then nothing happens. On the master, the node1 is shown as online and is connected to the VPN.
Currently I start Jenkins using a windows task. Using this method, the above happens only sometimes. But as I configured the server, I tried to solve this in a cleaner way by registering Jenkins as Windows Service. As Windows Service, I had the same behavior: In the web panel Node1 is shown as online, but when I start a job on it I only come to Build on slave node1 and then it stops.
Normally the next step should be fetching the latest source code from my git repo. I already had the problem but now found out that it has something to do how Jenkins is started. But for me it seems very strange because running the slave as a Windows Service hasn't worked at least one time, and by running it as a Task it works most of the time.
I only found out that the problem also occurs when I start a job directly after node1 boots. When I then cancel the hanging Job and start it again, it seems to work for a while.
There are few options that I can think of them. According to Jenkins Wiki
If the slave is supposed to start desktop applications you have to
allow the service to interact with the desktop
(Action->Properties->Logon->Allow service to interact with desktop).
Another option can be that Windows services don't have the ability to interact with the windows desktop, meaning that some UI tests might no work as you expect. Do any of the steps may need interacting with the desktop (Windows GUI)?
Just for the sports how about to setup a temporary clean windows server to act as node2 (Jenkins slave) and to check if the problem is been reproduced?
I am using Jenkins as my CI build server. After a build of our software is complete it starts up the automated tests on a slave machine. The tests that use a web browser run at a very good pace, the tests that run on two different local applications run very slowly. It takes about 3 seconds between each keystroke.
If I start the tests manually through Visual Studio 2010 on the same slave machine the local application test run just fine (fast keystrokes).
Any idea why the local apps are so slow when run through Jenkins?
I'm not sure if this is the same case, but we had similar issues with an automated UI test, and found that we must have a real session open on the slave running the test. NOT RDP.
We did this by using VNC to login to the slave and leave the session open.
I hope this helps.
I can't run any tess in VS2010. Even tests that have run before. I remember setting some services to manual start a few weeks ago, but can't remember what!
Problem: Which agent process / service do I need to start to make this work?
Edit: Even after uninstalling and reinstalling Studio2010 (and taking off the Novell Netware Client which I though may be an issue) it still doesn't work.
Got it! Avira Antivirus (even when 'disabled') seemed to be the culprit. Uninstall of the Antivirus made everything work again.
I'm using VS2015, I was experiencing the exact same error as the original poster (OP). My solution turned out to be simply turning on the add-on's within Internet Explorer so that I could start recording proper tests of my webapp. There were 3 or 4 add-on's that I simply had to enable. After I did that, this error "Unable to start agent process" never came back.