I have this very peculiar problem: When I launch the slave agent manually by right clicking and select launch, everything works normally and tests can be executed on that node.
However, when I launch the slave-agent via Windows Task Scheduler, Jenkins can see it and can launch tests on that node, although I do not see the slave-agent window in the node being active, and I can start tests from Jenkins on that node, but nothing runs at the node and eventually Jenkins fails the project. I have seen this problem several times already to the point where I'm afraid of using task scheduler anymore. I can not use the slave-agent as a service because I'm running UI Tests. Have anyone seen this problem and have you found a solution? I'm using Jenkins 2.164.3 in Windows. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/e52eb911-4006-448a-9bf3-faa0ab705003%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
