I'm not quite sure what you mean.
The other user logs on to jenkins on the server (or triggers a build with
his name and password in the url, same thing in effect), but the slave is
started by me and runs in my user space (which has admin priviledges).. or
so I thought, the fact that things fai
Just a quick question just in case, does you other user log on the machine
and the Jenkins is start with the other user space? Windows have a stupid
behavior of limiting the number of user that can be loggon at the same
time. Probably not the case, but just to make sure, run Jenkins into a
serv
Further investigation shows that if I log in as third user,windows builds
fail in the same way.
So it seems the determining factor is which user triggers the build,
despite the fact that they all have admin priviiedges.
Some help on this would be much appreciates. It's taken me ages to get
the
After deleting the relevant workspace folder and getting my colleague to
trigger another build, I get a different, but I suspect related, error
java.io.IOException: remote file operation failed:
C:\Jenkins\workspace\WPF\TryBuild\Hugo Brangwyn\PluginWrapper at
hudson.remoting.Channel@6b81cdda:C
Hi,
I've set up a try-before-commit build using the pipeline, and a script on
the client that sends a diff and starts a build.
Now if I run this, it works fine (the jenkins machines are on my local
network, but I access them through a global url)
However if my colleague runs it, then everythin
