That sounds like a bug. Is this with the long-term support release (2.89.3) or with a weekly release (like 2.102).
If it is a weekly release, is the same problem visible in a weekly release prior to 2.102? The 2.102 release includes a security improvement (JEP-200) which detected several places that need further changes. If it is with LTS or an earlier weekly release, submit a bug report ( https://wiki.jenkins.io/display/JENKINS/How+to+report+an+issue ). Mark Waite On Sun, Jan 21, 2018 at 7:04 PM Giles Gaskell <ggask...@cloudbees.com> wrote: > Hi all, > > I recently saw someone raise this issue > <https://github.com/jenkins-docs/simple-java-maven-app/issues/11> in the > GitHub repository that the Build a Java app with Maven > <https://jenkins.io/doc/tutorials/build-a-java-app-with-maven/> tutorial > uses. > > This issue shows the output of the Pipeline run with the typical failures > that happen fairly early on: > > sh: can't create > /var/jenkins_home/workspace/sjma@tmp/durable-cd13b59e/jenkins-log.txt: >> nonexistent directory >> sh: can't create >> /var/jenkins_home/workspace/sjma@tmp/durable-cd13b59e/jenkins-result.txt: >> nonexistent directory > > > I even began running though this tutorial myself and encountered the same > problem... I would also expect the same problematic output in most of the > other tutorials. > > Essentially, the tutorial asks the reader to do the following: > > 1. Install Jenkins in Docker (locally on your computer). > 2. Fork the sample GitHub repository and clone it locally to your > computer. > 3. Create your Jenkinsfile within your locally cloned repo on the your > computer. > 4. Run the declarative Pipeline in Jenkins. > > Puzzled as to why this might be happening, I found this closed issue > <https://github.com/jenkinsci/docker/issues/626> in the jenkinsci/docker > GitHub project which seems to shed a bit of light on the problem. However, > I wasn't quite sure if the actual problem (be it a change or issue with the > Jenkins Docker image or Docker itself) was clearly identified. > > Since lots of people use these tutorials (i.e. from September/October last > year, over 900 people have forked the simple-java-maven-app repository > used by this first tutorial), I am keen to identify the cause of this issue > (and potentially fix the tutorial content asap so that the tutorials will > start working again). > > Therefore, does anyone here have any suggestions as what might be the > cause of this issue and/or how I might amend the tutorials to get them > working again. For example, are there additional options I could add to the > docker > run ... command? > > Many thanks, > Giles. > > P.S. I am keen to keep using the Jenkins Docker container method for > running Jenkins since this is a convenient way to get Jenkins up and > running locally. > > -- > 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/841d29f5-2ea5-48a0-bb2b-339a6f11a918%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/841d29f5-2ea5-48a0-bb2b-339a6f11a918%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CAO49JtGxfP6MN5iMdVjp-EZd6jbQCRACo5Hd0yWmhW-3N6A5SA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
