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?
On Fri, Aug 2, 2019 at 12:11 PM Nef Rey wrote:
> The problem was that I was selecting the option to start the slave task
> whether the user was logged on or
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.
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 nod
