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 these autobuilds to the point where I thought they could be rolled out, only to run into this On Thursday, November 24, 2016 at 4:32:36 PM UTC, Jonathan Hodgson wrote: > > > 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:Channel to /82.39.249.244: > java.io.IOException: Failed to extract changes.patch.tar.gz > at hudson.FilePath.act(FilePath.java:992) > at hudson.FilePath.act(FilePath.java:974) > at hudson.FilePath.untar(FilePath.java:527) > at > org.jenkinsci.plugins.workflow.flow.StashManager.unstash(StashManager.java:122) > at > org.jenkinsci.plugins.workflow.support.steps.stash.UnstashStep$Execution.run(UnstashStep.java:64) > at > org.jenkinsci.plugins.workflow.support.steps.stash.UnstashStep$Execution.run(UnstashStep.java:54) > > > > It looks like remote file operations are failing on the windows slave, but > only in builds that he triggered. This makes no sense to me since as I > understand it, any operations on the slave run with permissions determined > by the user that started the jenkins slave, not the user triggering a build > -- 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-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/082f4976-6084-46b4-920c-c810ab151a10%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
