Re: Pipeline build crashes depending on who started it?

2016-11-25 Thread Jonathan Hodgson
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 fail make me wonder if that mechanism 
works as I thought. 

Everything is done through jenkins, people aren't logging on to the machine 
itself.

On Friday, November 25, 2016 at 4:10:49 PM UTC, jer...@bodycad.com wrote:
>
> 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 
> service admin so it doesn't get kill when the other user login.
>

-- 
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/6e4366d3-3a48-4bc2-93f7-b5925c2914d8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Pipeline build crashes depending on who started it?

2016-11-25 Thread jerome
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 
service admin so it doesn't get kill when the other user login.

-- 
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/be1d9b5a-155c-4723-8b31-f1531bb79557%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Pipeline build crashes depending on who started it?

2016-11-24 Thread Jonathan Hodgson
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.


Re: Pipeline build crashes depending on who started it?

2016-11-24 Thread Jonathan Hodgson

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/94b709dc-0938-4468-a4ae-a15fab967768%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Pipeline build crashes depending on who started it?

2016-11-24 Thread Jonathan Hodgson
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 everything on the master (Debian 
Linux) and the OSX build slave runs correctly, but the windows build slave 
crashes, with

java.io.IOException: Failed to mkdirs: C:\Jenkins\workspace\WPF\TryBuild\Hugo 
Brangwyn\PluginWrapper@tmp\durable-fffd693e
at hudson.FilePath.mkdirs(FilePath.java:1169)
at 
org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController.(FileMonitoringTask.java:101)
at 
org.jenkinsci.plugins.durabletask.WindowsBatchScript$BatchController.(WindowsBatchScript.java:94)
at 
org.jenkinsci.plugins.durabletask.WindowsBatchScript$BatchController.(WindowsBatchScript.java:92)
at 
org.jenkinsci.plugins.durabletask.WindowsBatchScript.doLaunch(WindowsBatchScript.java:60)
at 
org.jenkinsci.plugins.durabletask.FileMonitoringTask.launchWithCookie(FileMonitoringTask.java:66)
at 
org.jenkinsci.plugins.durabletask.FileMonitoringTask.launch(FileMonitoringTask.java:61)
at 
org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.start(DurableTaskStep.java:158)
at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:184)
at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:126)
at 
org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:108)
at groovy.lang.GroovyObject$invokeMethod$8.call(Unknown Source)
at 
org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
at 
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)
at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:151)
at 
org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:21)
at 
org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:115)
at 
org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:103)
at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:149)
at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:146)
at 
com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:16)
at 
gforce.Mercurial.cleanupWorkingCopy(file:/var/lib/jenkins/jobs/WPF/jobs/TryBuild/builds/461/libs/gforce/src/gforce/Mercurial.groovy:16)
at 
gforce.Mercurial.tryCheckOutWithPatch(file:/var/lib/jenkins/jobs/WPF/jobs/TryBuild/builds/461/libs/gforce/src/gforce/Mercurial.groovy:32)
at 
gforce.Mercurial.tryCheckOut(file:/var/lib/jenkins/jobs/WPF/jobs/TryBuild/builds/461/libs/gforce/src/gforce/Mercurial.groovy:58)
at 
gforce.Mercurial.checkoutBuild(file:/var/lib/jenkins/jobs/WPF/jobs/TryBuild/builds/461/libs/gforce/src/gforce/Mercurial.groovy:93)
at Script1.buildAll(Script1.groovy:198)
at ___cps.transform___(Native Method)
at 
com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:57)
at 
com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:109)
at 
com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:82)
at sun.reflect.GeneratedMethodAccessor515.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)
at 
com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:103)
at 
com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:82)
at sun.reflect.GeneratedMethodAccessor515.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)
at 
com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:60)
at 
com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:109)
at 
com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:82)
at sun.reflect.GeneratedMethodAccessor515.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at