[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title Waldek M edited a comment on JENKINS-33510 Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes [~jinzoo] Have you given the example you wanted here? The Jenkinsfile you posted doesn't use dir () . Also, did you mean to use `sh "echo $PWD"` ? Also, you did specify "-u root" in run args, which is exactly what you got. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168928.1457906095000.5976.1583971981289%40Atlassian.JIRA.
[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title Waldek M commented on JENKINS-33510 Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes john dow Have you given the example you wanted here? The Jenkinsfile you posted doesn't use dir () . Also, did you mean to use `sh "echo $PWD"` ? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168928.1457906095000.5899.1583971801425%40Atlassian.JIRA.
[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title john dow commented on JENKINS-33510 Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes I am still seeing this issue with Docker Pipeline v 1.22 and Docker v 19.03 Jenkinfile: pipeline { agent { docker { image 'ruby' args '-u root' } } stages { stage('build') { steps { sh '$PWD' sh 'ruby --version' } } } I get the following error: $ docker run -t -d -u 1000:996 -u root -w /var/jenkins_home/workspace/build-chef-pkgs --volumes-from 0d3a069ee976a6e027b7605d0b4d3abada6bcc9c1b1afcaf5ffa0610e4e83b76 -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e ruby cat $ docker top c9b3ddcd8df5ea3e447f163006cd42a057ca55eea49f6df1c806d0e010459bfc -eo pid,comm [Pipeline] { [Pipeline] stage [Pipeline] { (build) [Pipeline] sh + /var/jenkins_home/workspace/build-chef-pkgs /var/jenkins_home/workspace/build-chef-pkgs@tmp/durable-e13f4856/script.sh: 1: /var/jenkins_home/workspace/build-chef-pkgs@tmp/durable-e13f4856/script.sh: /var/jenkins_home/workspace/build-chef-pkgs: Permission denied The working directory is mounted as root and I cannot override the default user or working directory arguments passed to the docker run command Add Comment This message was sent by Atlassian Jira (v7.13.12#71301
[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title p cowlinator edited a comment on JENKINS-33510 Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes FYI, you need Docker Pipeline plugin v 1.15+ and Docker v 17.12+ in order to see this fix. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168928.1457906095000.1564.1579299001669%40Atlassian.JIRA.
[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title p cowlinator commented on JENKINS-33510 Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes FYI, you need Docker Pipeline plugin v 1.15+ in order to see this fix. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168928.1457906095000.1492.1579298882138%40Atlassian.JIRA.
[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title Jesse Glick commented on JENKINS-33510 Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes Attila Szeremi dir with an absolute path is not supported inside a Docker container. Not really related to this issue. Simply start your sh script with cd. Or avoid using the withDockerContainer step alogether—if it works perfectly for you out of the box, great, otherwise forget about it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title Attila Szeremi edited a comment on JENKINS-33510 Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes [~duemir] oh, so it needs to create a directory like that as a sort of preparation.But it doesn't make sense to me how it's expecting for the parent of the workdir to be writable.I thought `/var/www` is fine for a workdir, but of course `/var` wouldn't be writable to the default user under normal circumstances. [ + A popular article + |https://buddy.works/guides/how-dockerize-node-application] suggests to use `/app` as the workdir, where of course `/` wouldn't be writable. Why isn't Docker writing to `/var/tmp` instead which is writable? What am I (or others) expected to do instead? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title Attila Szeremi commented on JENKINS-33510 Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes Denys Digtiar oh, so it needs to create a directory like that as a sort of preparation. But it doesn't make sense to me how it's expecting for the parent of the workdir to be writable. I thought `/var/www` is fine for a workdir, but of course `/var` wouldn't be writable to the default user under normal circumstances. A popular article suggests to use `/app` as the workdir, where of course `/` wouldn't be writable. Why isn't Docker writing to `/var/tmp` instead which is writable? What am I (or others) expected to do instead? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title Denys Digtiar commented on JENKINS-33510 Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes Attila Szeremi So the defect indeed looks fixed and the issue appears to be with the file access now. Jenkins is trying to create a temp working directory besides the current working directory to write a shell script to but doesn't seem to have access to the `/var` directory. I would recommend reaching out to the mailing list or StackOverflow to get help with it if you have not yet solved it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title Attila Szeremi edited a comment on JENKINS-33510 Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes [~duemir] I have Docker Pipeline plugin 1.17, and Docker version 18.09.0. And doing dir in + [my Jenkinsfile|https://github.com/amcsi/youtube-delete-tracker/blob/723ab7a9fcb508608141abbcd1615740c1d63264/Jenkinsfile.groovy] + got me... {code:java}[Pipeline] {[Pipeline] stage[Pipeline] { (Run tests)[Pipeline] dirRunning in /var/www[Pipeline] {[Pipeline] sh[Pipeline] }[Pipeline] // dir[Pipeline] }[Pipeline] // stage[Pipeline] }$ docker stop --time=1 baa0c2d74c1fdc4944eb4e0bb5eb57f8435caac1a2e28ab562140bb3e0daaf38$ docker rm -f baa0c2d74c1fdc4944eb4e0bb5eb57f8435caac1a2e28ab562140bb3e0daaf38[Pipeline] // withDockerContainer[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineGitHub has been notified of this commit’s build resultjava.nio.file.AccessDeniedException: /var/www@tmp at sun.nio.fs.UnixException.translateToIOException(UnixException.java:84) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) at sun.nio.fs.UnixFileSystemProvider.createDirectory(UnixFileSystemProvider.java:384) at java.nio.file.Files.createDirectory(Files.java:674) at java.nio.file.Files.createAndCheckIsDirectory(Files.java:781) at java.nio.file.Files.createDirectories(Files.java:767) at hudson.FilePath.mkdirs(FilePath.java:3273) at hudson.FilePath.access$1300(FilePath.java:213) at hudson.FilePath$Mkdirs.invoke(FilePath.java:1254) at hudson.FilePath$Mkdirs.invoke(FilePath.java:1250) at hudson.FilePath.act(FilePath.java:1078) at hudson.FilePath.act(FilePath.java:1061) at hudson.FilePath.mkdirs(FilePath.java:1246) at org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController.(FileMonitoringTask.java:174) at org.jenkinsci.plugins.durabletask.BourneShellScript$ShellController.(BourneShellScript.java:200) at org.jenkinsci.plugins.durabletask.BourneShellScript$ShellController.(BourneShellScript.java:192) at org.jenkinsci.plugins.durabletask.BourneShellScript.launchWithCookie(BourneShellScript.java:110) at org.jenkinsci.plugins.durabletask.FileMonitoringTask.launch(FileMonitoringTask.java:99) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.start(DurableTaskStep.java:278) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:270) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:178) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) at sun.reflect.GeneratedMethodAccessor312.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1213) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:42) 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:157) at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:23) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:155) at org.kohsuke.groovy.sandbox.impl.Checker
[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title Attila Szeremi edited a comment on JENKINS-33510 Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes [~duemir] I have Docker Pipeline plugin 1.17, and Docker version 18.09.0. And `sh 'pwd'` still gives me {{ doing dir in [my Jenkinsfile|https: / var / jenkins_home github.com / workspace amcsi /youtube-delete- tracker_cd tracker/blob/723ab7a9fcb508608141abbcd1615740c1d63264/Jenkinsfile.groovy] got me... {code:java } } rather than my expected Docker workdir which is [Pipeline] { [Pipeline] stage[Pipeline] { (Run tests)[Pipeline] dirRunning in /var/www [Pipeline] {[Pipeline] sh[Pipeline] } [Pipeline] // dir[Pipeline] } [Pipeline] // stage[Pipeline] }$ docker stop --time=1 baa0c2d74c1fdc4944eb4e0bb5eb57f8435caac1a2e28ab562140bb3e0daaf38$ docker rm -f baa0c2d74c1fdc4944eb4e0bb5eb57f8435caac1a2e28ab562140bb3e0daaf38[Pipeline] // withDockerContainer[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineGitHub has been notified of this commit’s build resultjava . nio.file.AccessDeniedException: /var/www@tmp at sun.nio.fs.UnixException.translateToIOException(UnixException.java:84) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) at sun.nio.fs.UnixFileSystemProvider.createDirectory(UnixFileSystemProvider.java:384) at java.nio.file.Files.createDirectory(Files.java:674) at java.nio.file.Files.createAndCheckIsDirectory(Files.java:781) at java.nio.file.Files.createDirectories(Files.java:767) at hudson.FilePath.mkdirs(FilePath.java:3273) at hudson.FilePath.access$1300(FilePath.java:213) at hudson.FilePath$Mkdirs.invoke(FilePath.java:1254) at hudson.FilePath$Mkdirs.invoke(FilePath.java:1250) at hudson.FilePath.act(FilePath.java:1078) at hudson.FilePath.act(FilePath.java:1061) at hudson.FilePath.mkdirs(FilePath.java:1246) at org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController.(FileMonitoringTask.java:174) at org.jenkinsci.plugins.durabletask.BourneShellScript$ShellController.(BourneShellScript.java:200) at org.jenkinsci.plugins.durabletask.BourneShellScript$ShellController.(BourneShellScript.java:192) at org.jenkinsci.plugins.durabletask.BourneShellScript.launchWithCookie(BourneShellScript.java:110) at org.jenkinsci.plugins.durabletask.FileMonitoringTask.launch(FileMonitoringTask.java:99) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.start(DurableTaskStep.java:278) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:270) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:178) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) at sun.reflect.GeneratedMethodAccessor312.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1213) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:42) 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:157) at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:23) at org.jenkinsci.plugins.scri
[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title Attila Szeremi commented on JENKINS-33510 Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes Denys Digtiar I have Docker Pipeline plugin 1.17, and Docker version 18.09.0. And `sh 'pwd'` still gives me /var/jenkins_home/workspace/youtube-delete-tracker_cd rather than my expected Docker workdir which is /var/www. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title Denys Digtiar edited a comment on JENKINS-33510 Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes [~amcsi] If you Docker Pipeline plugin is 1.15 and Docker is 17.12 or newer then everything should just work no need to change the Pipeline . That is if I understand the fix correctly. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title Denys Digtiar commented on JENKINS-33510 Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes Attila Szeremi If you Docker Pipeline plugin is 1.15 and Docker is 17.12 or newer then everything should just work no need to change the Pipeline Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title Attila Szeremi commented on JENKINS-33510 Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes This ticket is supposedly resolved... but then what do I need to write to make sure the `sh` commands are run in the correct working directory? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title Michael Neale commented on JENKINS-33510 Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes thanks Waldek M - they most certainly are as they are using docker pipeline under the covers at the moment. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title Waldek M commented on JENKINS-33510 Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes I took the liberty to link JENKINS-38331 - per-stage `agent` declarations are also affected. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title Denis Boulas updated an issue Jenkins / JENKINS-33510 dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes Change By: Denis Boulas Priority: Minor Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title Michael Neale commented on JENKINS-33510 Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes Christian Höltje ha - no I think its just as this was referred to in a commit message in a pull request, and JIRA automatically picks it up (not directly related to this issue, but was impacted by it). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title Christian Höltje commented on JENKINS-33510 Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes I was trying to figure out if it was some weird spam or what... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title Michael Neale commented on JENKINS-33510 Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes Tom FENNELLY I enjoy your amusing squashed git commit comments Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title Abdulaziz Alfoudari edited a comment on JENKINS-33510 Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes Until there is a fix, a quick around workaround is to append prepend `cd foo &&` to each `sh` inside `dir('foo')`:{code}dir('foo') {sh 'cd foo && make'}{code} Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33510 Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes Code changed in jenkins User: Tom Fennelly Path: .printip.js Dockerfile Jenkinsfile nightwatch.conf.js package.json run.sh src/main/java/io/jenkins/blueocean/BOJUnitTest.java src/main/java/io/jenkins/blueocean/BlueOceanWinstoneController.java src/main/java/io/jenkins/blueocean/NightwatchRunner.java src/main/js/custom_commands/moveClassicBottomStickyButtons.js src/main/js/custom_commands/moveConfigpageButtons.js src/main/js/custom_commands/removeBreadcrumbBar.js src/main/js/custom_commands/removePageHead.js src/main/js/globals.js src/main/js/page_objects/blueocean/bluePipelineActivity.js src/main/js/page_objects/classic_jenkins/folderCreate.js src/main/js/page_objects/classic_jenkins/freestyleConfig.js src/main/js/page_objects/classic_jenkins/freestyleCreate.js src/main/js/page_objects/classic_jenkins/multibranchCreate.js src/main/js/page_objects/classic_jenkins/pipelineCreate.js src/main/nightwatch.json src/test/java/utils/DevRunner.java start-selenium.sh stop-selenium.sh http://jenkins-ci.org/commit/blueocean-acceptance-test/6aac5c09b5614833cb2bcd78bc346a7e4dd0c2da Log: More ATH shenanigans + a Jenkinsfile (#44) Added a simple Jenkinsfile Use docker-selenium images Use official images in the local start selenium scripts More tweaking of the Jenkinsfile And more tweaking of the Jenkinsfile again what's the pwd what's the pwd what's the pwd Map in a volume for ~/.m2 Map in a volume for ~/.m2 No clue what I'm doing revert BS tests
[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title Sean Gilhooly commented on JENKINS-33510 Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes I might have a different bug that has the same outcome but my script does not have any dir calls in it. With just a sh command I get this error. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title Abdulaziz Alfoudari commented on JENKINS-33510 Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes Until there is a fix, a quick around is to append `cd foo &&` to each `sh` inside `dir('foo')`: dir('foo') { sh 'cd foo && make' } Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title Sean Gilhooly commented on JENKINS-33510 Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes Given this is cataloged as a "Minor" issue, is there a workaround for this? This appears to render this plugin unusable from what I observe. My fairly simple script: docker.image("...").inside("--args...") { sh "gradle build" } can't get anywhere: sh: /var/jenkins_home/workspace/job@tmp/durable-b85d7f08/pid: No such file or directory sh: /var/jenkins_home/workspace/job@tmp/durable-b85d7f08/jenkins-log.txt: No such file or directory sh: /var/jenkins_home/workspace/job@tmp/durable-b85d7f08/jenkins-result.txt: No such file or directory Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optou
[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33510 Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes Code changed in jenkins User: tfennelly Path: Jenkinsfile http://jenkins-ci.org/commit/blueocean-acceptance-test/9960c382dd960de23c320392842e9959c49feb5f Log: Ok ... needed plugins update and also see JENKINS-33510 ffs Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33510 Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes Code changed in jenkins User: tfennelly Path: Jenkinsfile http://jenkins-ci.org/commit/blueocean-acceptance-test/e13cec063b8bcc45358ab0bda151ec280ac7bf77 Log: Ok ... needed plugins update and also see JENKINS-33510 ffs Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title Tom FENNELLY commented on JENKINS-33510 Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes This had me scratching my head for a while. Glad to see there's a fix in progress. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-33510 dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes Change By: Jesse Glick Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title Wilfried Goesgens commented on JENKINS-33510 Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes This constellation: docker.image('foo').inside { node { sh 'pwd' } fails for me too with:_ [ArangoDB_Devel_Build@2] Running shell script JENKINS-33510: working directory will be /var/lib/jenkins/workspace/ArangoDB_Devel_Build not /var/lib/jenkins/workspace/ArangoDB_Devel_Build@2 sh: /var/lib/jenkins/workspace/ArangoDB_Devel_Build@2@tmp/durable-0b92a427/pid: No such file or directory sh: /var/lib/jenkins/workspace/ArangoDB_Devel_Build@2@tmp/durable-0b92a427/jenkins-log.txt: No such file or directory sh: /var/lib/jenkins/workspace/ArangoDB_Devel_Build@2@tmp/durable-0b92a427/jenkins-result.txt: No such file or directory_ I guess thats an artifact of this problem? is one discouraged to do that? Or will it be fixed? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title Michael Neale commented on JENKINS-33510 Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes Jesse Glick I see the PR 38 for this was merged - so a new release of docker pipeline will close this right? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title Michael Neale started work on JENKINS-33510 Change By: Michael Neale Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title Michael Neale commented on JENKINS-33510 Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes This has been annoying me of late. I would like to work with multiple checked out repos using docker.inside, but this makes it difficult Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.