WebStart Slave-Agent misbehaving when launched via Windows Task Scheduler

[Nef Rey]

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.

[Nef Rey]

The problem was that I was selecting the option to start the slave task whether the user was logged on or not. This option was blocked in our company policy.  Weird that slave acted as if everything was alright  but, misbehaved.  I had to select the option to start when the user was logged on.  And additionally I had to also specify the "Start in (optional)" option in the task so windows knows the path where to begin.

[Slide]

It might be better to run the agent as a service under the specific account you want it to run under. Is there a reason you can't do this?

--
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 jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1c7a5205-1f41-4781-9b5d-dc2c9e0f1fbe%40googlegroups.com.

--

Website: http://earl-of-code.com