Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-39307

pipeline docker execution aborts without reason

XMLWordPrintable

      I'm trying to compile ArangoDB in one of these docker containers:
      https://github.com/arangodb-helper/build-docker-containers/tree/master/distros
      It works flawless for most of the containers, however I've seen it abort without any reason for docker containers derived of these two base contaires:

      fedora:23 ubuntu:12.04

      The output in the webinterface looks like that:

      [ 24%] Building CXX object lib/CMakeFiles/arango.dir/ApplicationFeatures/ApplicationServer.cpp.o
  CXX(target) /var/lib/jenkins/workspace/ArangoDB_Release/build-EPpackage-ubuntutwelveofour/3rdParty/V8/v8/x64.release/obj.target/icui18n/third_party/icu/source/i18n/fpositer.o
  CXX(target) /var/lib/jenkins/workspace/ArangoDB_Release/build-EPpackage-ubuntutwelveofour/3rdParty/V8/v8/x64.release/obj.target/icui18n/third_party/icu/source/i18n/funcrepl.o
  CXX(target) /var/lib/jenkins/workspace/ArangoDB_Release/build-EPpackage-ubuntutwelveofour/3rdParty/V8/v8/x64.release/obj.target/icui18n/third_party/icu/source/i18n/gender.o

  CXX(target) /var/lib/jenkins/workspace/ArangoDB_Release/build-EPpackage-ubuntutwelveofour/3rdParty/V8/v8/x64.release/obj.target/icui18n/third_party/icu/source/i18n/gregocal.o
[ 24%] Building CXX object 3rdParty/rocksdb/rocksdb/CMakeFiles/rocksdblib.dir/db/db_iter.cc.o
  CXX(target) /var/lib/jenkins/workspace/ArangoDB_Release/build-EPpackage-ubuntutwelveofour/3rdParty/V8/v8/x64.release/obj.target/icui18n/third_party/icu/source/i18n/gregoimp.o
[Pipeline] stage
[Pipeline] { (Send Notification for failed build)
[Pipeline] sh
[ArangoDB_Release] Running shell script
+ git --no-pager show -s --format=%ae
[Pipeline] mail

[Pipeline] }
[Pipeline] // stage

[Pipeline] }
$ docker stop --time=1 e0c5a42869989172c87fd272a714980602d7ec6c6b1be4655589b23f88b54760
$ docker rm -f e0c5a42869989172c87fd272a714980602d7ec6c6b1be4655589b23f88b54760
[Pipeline] // withDockerContainer
[Pipeline] }
[Pipeline] // withDockerRegistry
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] stage (Send Notification for build)
Using the ‘stage’ step without a block argument is deprecated
Entering stage Send Notification for build
Proceeding
[Pipeline] mail

      In the Ubuntu 12 container. In the Fedora container, it barely gets to start running the configure part of cmake and aborts that in a similar manner without any particular reason.

      When running the container on an interactive terminal session, the whole build goes through without any issues.

          [JENKINS-39307] pipeline docker execution aborts without reason

          Wilfried Goesgens created issue -
          Wilfried Goesgens made changes -
          Description Original: I'm trying to compile ArangoDB in one of these docker containers:
          https://github.com/arangodb-helper/build-docker-containers/tree/master/distros
          It works flawless for most of the containers, however I've seen it abort without any reason for docker containers derived of these two base contaires:

          fedora:23 ubuntu:12.04

          The output in the webinterface looks like that:


          [ 24%] Building CXX object lib/CMakeFiles/arango.dir/ApplicationFeatures/ApplicationServer.cpp.o
            CXX(target) /var/lib/jenkins/workspace/ArangoDB_Release/build-EPpackage-ubuntutwelveofour/3rdParty/V8/v8/x64.release/obj.target/icui18n/third_party/icu/source/i18n/fpositer.o
            CXX(target) /var/lib/jenkins/workspace/ArangoDB_Release/build-EPpackage-ubuntutwelveofour/3rdParty/V8/v8/x64.release/obj.target/icui18n/third_party/icu/source/i18n/funcrepl.o
            CXX(target) /var/lib/jenkins/workspace/ArangoDB_Release/build-EPpackage-ubuntutwelveofour/3rdParty/V8/v8/x64.release/obj.target/icui18n/third_party/icu/source/i18n/gender.o

            CXX(target) /var/lib/jenkins/workspace/ArangoDB_Release/build-EPpackage-ubuntutwelveofour/3rdParty/V8/v8/x64.release/obj.target/icui18n/third_party/icu/source/i18n/gregocal.o
          [ 24%] Building CXX object 3rdParty/rocksdb/rocksdb/CMakeFiles/rocksdblib.dir/db/db_iter.cc.o
            CXX(target) /var/lib/jenkins/workspace/ArangoDB_Release/build-EPpackage-ubuntutwelveofour/3rdParty/V8/v8/x64.release/obj.target/icui18n/third_party/icu/source/i18n/gregoimp.o
          [Pipeline] stage
          [Pipeline] { (Send Notification for failed build)
          [Pipeline] sh
          [ArangoDB_Release] Running shell script
          + git --no-pager show -s --format=%ae
          [Pipeline] mail

          [Pipeline] }
          [Pipeline] // stage

          [Pipeline] }
          $ docker stop --time=1 e0c5a42869989172c87fd272a714980602d7ec6c6b1be4655589b23f88b54760
          $ docker rm -f e0c5a42869989172c87fd272a714980602d7ec6c6b1be4655589b23f88b54760
          [Pipeline] // withDockerContainer
          [Pipeline] }
          [Pipeline] // withDockerRegistry
          [Pipeline] }
          [Pipeline] // withEnv
          [Pipeline] }
          [Pipeline] // node
          [Pipeline] stage (Send Notification for build)
          Using the ‘stage’ step without a block argument is deprecated
          Entering stage Send Notification for build
          Proceeding
          [Pipeline] mail
          		 New: I'm trying to compile ArangoDB in one of these docker containers:
          https://github.com/arangodb-helper/build-docker-containers/tree/master/distros
          It works flawless for most of the containers, however I've seen it abort without any reason for docker containers derived of these two base contaires:

          fedora:23 ubuntu:12.04

          The output in the webinterface looks like that:


          [ 24%] Building CXX object lib/CMakeFiles/arango.dir/ApplicationFeatures/ApplicationServer.cpp.o
            CXX(target) /var/lib/jenkins/workspace/ArangoDB_Release/build-EPpackage-ubuntutwelveofour/3rdParty/V8/v8/x64.release/obj.target/icui18n/third_party/icu/source/i18n/fpositer.o
            CXX(target) /var/lib/jenkins/workspace/ArangoDB_Release/build-EPpackage-ubuntutwelveofour/3rdParty/V8/v8/x64.release/obj.target/icui18n/third_party/icu/source/i18n/funcrepl.o
            CXX(target) /var/lib/jenkins/workspace/ArangoDB_Release/build-EPpackage-ubuntutwelveofour/3rdParty/V8/v8/x64.release/obj.target/icui18n/third_party/icu/source/i18n/gender.o

            CXX(target) /var/lib/jenkins/workspace/ArangoDB_Release/build-EPpackage-ubuntutwelveofour/3rdParty/V8/v8/x64.release/obj.target/icui18n/third_party/icu/source/i18n/gregocal.o
          [ 24%] Building CXX object 3rdParty/rocksdb/rocksdb/CMakeFiles/rocksdblib.dir/db/db_iter.cc.o
            CXX(target) /var/lib/jenkins/workspace/ArangoDB_Release/build-EPpackage-ubuntutwelveofour/3rdParty/V8/v8/x64.release/obj.target/icui18n/third_party/icu/source/i18n/gregoimp.o
          [Pipeline] stage
          [Pipeline] { (Send Notification for failed build)
          [Pipeline] sh
          [ArangoDB_Release] Running shell script
          + git --no-pager show -s --format=%ae
          [Pipeline] mail

          [Pipeline] }
          [Pipeline] // stage

          [Pipeline] }
          $ docker stop --time=1 e0c5a42869989172c87fd272a714980602d7ec6c6b1be4655589b23f88b54760
          $ docker rm -f e0c5a42869989172c87fd272a714980602d7ec6c6b1be4655589b23f88b54760
          [Pipeline] // withDockerContainer
          [Pipeline] }
          [Pipeline] // withDockerRegistry
          [Pipeline] }
          [Pipeline] // withEnv
          [Pipeline] }
          [Pipeline] // node
          [Pipeline] stage (Send Notification for build)
          Using the ‘stage’ step without a block argument is deprecated
          Entering stage Send Notification for build
          Proceeding
          [Pipeline] mail


          In the Ubuntu 12 container. In the Fedora container, it barely gets to start running the configure part of cmake and aborts that in a similar manner without any particular reason.
          Wilfried Goesgens made changes -
          Description Original: I'm trying to compile ArangoDB in one of these docker containers:
          https://github.com/arangodb-helper/build-docker-containers/tree/master/distros
          It works flawless for most of the containers, however I've seen it abort without any reason for docker containers derived of these two base contaires:

          fedora:23 ubuntu:12.04

          The output in the webinterface looks like that:


          [ 24%] Building CXX object lib/CMakeFiles/arango.dir/ApplicationFeatures/ApplicationServer.cpp.o
            CXX(target) /var/lib/jenkins/workspace/ArangoDB_Release/build-EPpackage-ubuntutwelveofour/3rdParty/V8/v8/x64.release/obj.target/icui18n/third_party/icu/source/i18n/fpositer.o
            CXX(target) /var/lib/jenkins/workspace/ArangoDB_Release/build-EPpackage-ubuntutwelveofour/3rdParty/V8/v8/x64.release/obj.target/icui18n/third_party/icu/source/i18n/funcrepl.o
            CXX(target) /var/lib/jenkins/workspace/ArangoDB_Release/build-EPpackage-ubuntutwelveofour/3rdParty/V8/v8/x64.release/obj.target/icui18n/third_party/icu/source/i18n/gender.o

            CXX(target) /var/lib/jenkins/workspace/ArangoDB_Release/build-EPpackage-ubuntutwelveofour/3rdParty/V8/v8/x64.release/obj.target/icui18n/third_party/icu/source/i18n/gregocal.o
          [ 24%] Building CXX object 3rdParty/rocksdb/rocksdb/CMakeFiles/rocksdblib.dir/db/db_iter.cc.o
            CXX(target) /var/lib/jenkins/workspace/ArangoDB_Release/build-EPpackage-ubuntutwelveofour/3rdParty/V8/v8/x64.release/obj.target/icui18n/third_party/icu/source/i18n/gregoimp.o
          [Pipeline] stage
          [Pipeline] { (Send Notification for failed build)
          [Pipeline] sh
          [ArangoDB_Release] Running shell script
          + git --no-pager show -s --format=%ae
          [Pipeline] mail

          [Pipeline] }
          [Pipeline] // stage

          [Pipeline] }
          $ docker stop --time=1 e0c5a42869989172c87fd272a714980602d7ec6c6b1be4655589b23f88b54760
          $ docker rm -f e0c5a42869989172c87fd272a714980602d7ec6c6b1be4655589b23f88b54760
          [Pipeline] // withDockerContainer
          [Pipeline] }
          [Pipeline] // withDockerRegistry
          [Pipeline] }
          [Pipeline] // withEnv
          [Pipeline] }
          [Pipeline] // node
          [Pipeline] stage (Send Notification for build)
          Using the ‘stage’ step without a block argument is deprecated
          Entering stage Send Notification for build
          Proceeding
          [Pipeline] mail


          In the Ubuntu 12 container. In the Fedora container, it barely gets to start running the configure part of cmake and aborts that in a similar manner without any particular reason.
          		 New: I'm trying to compile ArangoDB in one of these docker containers:
          https://github.com/arangodb-helper/build-docker-containers/tree/master/distros
          It works flawless for most of the containers, however I've seen it abort without any reason for docker containers derived of these two base contaires:

          fedora:23 ubuntu:12.04

          The output in the webinterface looks like that:


          [ 24%] Building CXX object lib/CMakeFiles/arango.dir/ApplicationFeatures/ApplicationServer.cpp.o
            CXX(target) /var/lib/jenkins/workspace/ArangoDB_Release/build-EPpackage-ubuntutwelveofour/3rdParty/V8/v8/x64.release/obj.target/icui18n/third_party/icu/source/i18n/fpositer.o
            CXX(target) /var/lib/jenkins/workspace/ArangoDB_Release/build-EPpackage-ubuntutwelveofour/3rdParty/V8/v8/x64.release/obj.target/icui18n/third_party/icu/source/i18n/funcrepl.o
            CXX(target) /var/lib/jenkins/workspace/ArangoDB_Release/build-EPpackage-ubuntutwelveofour/3rdParty/V8/v8/x64.release/obj.target/icui18n/third_party/icu/source/i18n/gender.o

            CXX(target) /var/lib/jenkins/workspace/ArangoDB_Release/build-EPpackage-ubuntutwelveofour/3rdParty/V8/v8/x64.release/obj.target/icui18n/third_party/icu/source/i18n/gregocal.o
          [ 24%] Building CXX object 3rdParty/rocksdb/rocksdb/CMakeFiles/rocksdblib.dir/db/db_iter.cc.o
            CXX(target) /var/lib/jenkins/workspace/ArangoDB_Release/build-EPpackage-ubuntutwelveofour/3rdParty/V8/v8/x64.release/obj.target/icui18n/third_party/icu/source/i18n/gregoimp.o
          [Pipeline] stage
          [Pipeline] { (Send Notification for failed build)
          [Pipeline] sh
          [ArangoDB_Release] Running shell script
          + git --no-pager show -s --format=%ae
          [Pipeline] mail

          [Pipeline] }
          [Pipeline] // stage

          [Pipeline] }
          $ docker stop --time=1 e0c5a42869989172c87fd272a714980602d7ec6c6b1be4655589b23f88b54760
          $ docker rm -f e0c5a42869989172c87fd272a714980602d7ec6c6b1be4655589b23f88b54760
          [Pipeline] // withDockerContainer
          [Pipeline] }
          [Pipeline] // withDockerRegistry
          [Pipeline] }
          [Pipeline] // withEnv
          [Pipeline] }
          [Pipeline] // node
          [Pipeline] stage (Send Notification for build)
          Using the ‘stage’ step without a block argument is deprecated
          Entering stage Send Notification for build
          Proceeding
          [Pipeline] mail


          In the Ubuntu 12 container. In the Fedora container, it barely gets to start running the configure part of cmake and aborts that in a similar manner without any particular reason.

          When running the container on an interactive terminal session, the whole build goes through without any issues.
          Jesse Glick made changes -
          Description Original: I'm trying to compile ArangoDB in one of these docker containers:
          https://github.com/arangodb-helper/build-docker-containers/tree/master/distros
          It works flawless for most of the containers, however I've seen it abort without any reason for docker containers derived of these two base contaires:

          fedora:23 ubuntu:12.04

          The output in the webinterface looks like that:


          [ 24%] Building CXX object lib/CMakeFiles/arango.dir/ApplicationFeatures/ApplicationServer.cpp.o
            CXX(target) /var/lib/jenkins/workspace/ArangoDB_Release/build-EPpackage-ubuntutwelveofour/3rdParty/V8/v8/x64.release/obj.target/icui18n/third_party/icu/source/i18n/fpositer.o
            CXX(target) /var/lib/jenkins/workspace/ArangoDB_Release/build-EPpackage-ubuntutwelveofour/3rdParty/V8/v8/x64.release/obj.target/icui18n/third_party/icu/source/i18n/funcrepl.o
            CXX(target) /var/lib/jenkins/workspace/ArangoDB_Release/build-EPpackage-ubuntutwelveofour/3rdParty/V8/v8/x64.release/obj.target/icui18n/third_party/icu/source/i18n/gender.o

            CXX(target) /var/lib/jenkins/workspace/ArangoDB_Release/build-EPpackage-ubuntutwelveofour/3rdParty/V8/v8/x64.release/obj.target/icui18n/third_party/icu/source/i18n/gregocal.o
          [ 24%] Building CXX object 3rdParty/rocksdb/rocksdb/CMakeFiles/rocksdblib.dir/db/db_iter.cc.o
            CXX(target) /var/lib/jenkins/workspace/ArangoDB_Release/build-EPpackage-ubuntutwelveofour/3rdParty/V8/v8/x64.release/obj.target/icui18n/third_party/icu/source/i18n/gregoimp.o
          [Pipeline] stage
          [Pipeline] { (Send Notification for failed build)
          [Pipeline] sh
          [ArangoDB_Release] Running shell script
          + git --no-pager show -s --format=%ae
          [Pipeline] mail

          [Pipeline] }
          [Pipeline] // stage

          [Pipeline] }
          $ docker stop --time=1 e0c5a42869989172c87fd272a714980602d7ec6c6b1be4655589b23f88b54760
          $ docker rm -f e0c5a42869989172c87fd272a714980602d7ec6c6b1be4655589b23f88b54760
          [Pipeline] // withDockerContainer
          [Pipeline] }
          [Pipeline] // withDockerRegistry
          [Pipeline] }
          [Pipeline] // withEnv
          [Pipeline] }
          [Pipeline] // node
          [Pipeline] stage (Send Notification for build)
          Using the ‘stage’ step without a block argument is deprecated
          Entering stage Send Notification for build
          Proceeding
          [Pipeline] mail


          In the Ubuntu 12 container. In the Fedora container, it barely gets to start running the configure part of cmake and aborts that in a similar manner without any particular reason.

          When running the container on an interactive terminal session, the whole build goes through without any issues.
          		New: I'm trying to compile ArangoDB in one of these docker containers:
          https://github.com/arangodb-helper/build-docker-containers/tree/master/distros
          It works flawless for most of the containers, however I've seen it abort without any reason for docker containers derived of these two base contaires:

          fedora:23 ubuntu:12.04

          The output in the webinterface looks like that:

          {code:none}
          [ 24%] Building CXX object lib/CMakeFiles/arango.dir/ApplicationFeatures/ApplicationServer.cpp.o
            CXX(target) /var/lib/jenkins/workspace/ArangoDB_Release/build-EPpackage-ubuntutwelveofour/3rdParty/V8/v8/x64.release/obj.target/icui18n/third_party/icu/source/i18n/fpositer.o
            CXX(target) /var/lib/jenkins/workspace/ArangoDB_Release/build-EPpackage-ubuntutwelveofour/3rdParty/V8/v8/x64.release/obj.target/icui18n/third_party/icu/source/i18n/funcrepl.o
            CXX(target) /var/lib/jenkins/workspace/ArangoDB_Release/build-EPpackage-ubuntutwelveofour/3rdParty/V8/v8/x64.release/obj.target/icui18n/third_party/icu/source/i18n/gender.o

            CXX(target) /var/lib/jenkins/workspace/ArangoDB_Release/build-EPpackage-ubuntutwelveofour/3rdParty/V8/v8/x64.release/obj.target/icui18n/third_party/icu/source/i18n/gregocal.o
          [ 24%] Building CXX object 3rdParty/rocksdb/rocksdb/CMakeFiles/rocksdblib.dir/db/db_iter.cc.o
            CXX(target) /var/lib/jenkins/workspace/ArangoDB_Release/build-EPpackage-ubuntutwelveofour/3rdParty/V8/v8/x64.release/obj.target/icui18n/third_party/icu/source/i18n/gregoimp.o
          [Pipeline] stage
          [Pipeline] { (Send Notification for failed build)
          [Pipeline] sh
          [ArangoDB_Release] Running shell script
          + git --no-pager show -s --format=%ae
          [Pipeline] mail

          [Pipeline] }
          [Pipeline] // stage

          [Pipeline] }
          $ docker stop --time=1 e0c5a42869989172c87fd272a714980602d7ec6c6b1be4655589b23f88b54760
          $ docker rm -f e0c5a42869989172c87fd272a714980602d7ec6c6b1be4655589b23f88b54760
          [Pipeline] // withDockerContainer
          [Pipeline] }
          [Pipeline] // withDockerRegistry
          [Pipeline] }
          [Pipeline] // withEnv
          [Pipeline] }
          [Pipeline] // node
          [Pipeline] stage (Send Notification for build)
          Using the ‘stage’ step without a block argument is deprecated
          Entering stage Send Notification for build
          Proceeding
          [Pipeline] mail
          {code}

          In the Ubuntu 12 container. In the Fedora container, it barely gets to start running the configure part of cmake and aborts that in a similar manner without any particular reason.

          When running the container on an interactive terminal session, the whole build goes through without any issues.

          Jesse Glick added a comment -

          Steps to reproduce from scratch in a minimal, self-contained test case, please.

          Jesse Glick added a comment - Steps to reproduce from scratch in a minimal, self-contained test case, please.

          Wilfried Goesgens added a comment - - edited

          This pipeline script:

          stage("test") {
    node("docker") {
        docker.image("fedora:23").inside {
            sh """while /bin/true; do echo "."; sleep 1; done"""
        }
    }
}

          results in this output:

          [Pipeline] stage
[Pipeline] { (test)
[Pipeline] node
Running on master in /var/lib/jenkins/workspace/test fedora
[Pipeline] {
[Pipeline] sh
[test fedora] Running shell script
+ docker inspect -f . fedora:23
.
[Pipeline] withDockerContainer
$ docker run -t -d -u 1000:1000 -w "/var/lib/jenkins/workspace/test fedora" -v "/var/lib/jenkins/workspace/test fedora:/var/lib/jenkins/workspace/test fedora:rw" -v "/var/lib/jenkins/workspace/test fedora@tmp:/var/lib/jenkins/workspace/test fedora@tmp:rw" -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** --entrypoint cat fedora:23
[Pipeline] {
[Pipeline] sh
[test fedora] Running shell script
+ /bin/true
+ echo .
.
+ sleep 1
[Pipeline] }
$ docker stop --time=1 34e905df5f32c4409491799a51463c23ca8efae8fd9ab32e940f8aebb25ed034
$ docker rm -f 34e905df5f32c4409491799a51463c23ca8efae8fd9ab32e940f8aebb25ed034
[Pipeline] // withDockerContainer
[Pipeline] }
[Pipeline] // node
[Pipeline] }
[Pipeline] // stage
[Pipeline] End of Pipeline
ERROR: script returned exit code -1
Finished: FAILURE

          while i.e. using the docker image 'ubuntu:16.04 will result in an endless continuing 'echo .' list.

          Wilfried Goesgens added a comment - - edited This pipeline script: stage("test") { node("docker") { docker.image("fedora:23").inside { sh """while /bin/true; do echo "."; sleep 1; done""" } } } results in this output: [Pipeline] stage [Pipeline] { (test) [Pipeline] node Running on master in /var/lib/jenkins/workspace/test fedora [Pipeline] { [Pipeline] sh [test fedora] Running shell script + docker inspect -f . fedora:23 . [Pipeline] withDockerContainer $ docker run -t -d -u 1000:1000 -w "/var/lib/jenkins/workspace/test fedora" -v "/var/lib/jenkins/workspace/test fedora:/var/lib/jenkins/workspace/test fedora:rw" -v "/var/lib/jenkins/workspace/test fedora@tmp:/var/lib/jenkins/workspace/test fedora@tmp:rw" -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** --entrypoint cat fedora:23 [Pipeline] { [Pipeline] sh [test fedora] Running shell script + /bin/true + echo . . + sleep 1 [Pipeline] } $ docker stop --time=1 34e905df5f32c4409491799a51463c23ca8efae8fd9ab32e940f8aebb25ed034 $ docker rm -f 34e905df5f32c4409491799a51463c23ca8efae8fd9ab32e940f8aebb25ed034 [Pipeline] // withDockerContainer [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] End of Pipeline ERROR: script returned exit code -1 Finished: FAILURE while i.e. using the docker image 'ubuntu:16.04 will result in an endless continuing 'echo .' list.

          Jesse Glick added a comment -

          BTW please use {code:none}…{code} in JIRA to make issues legible. (I could edit your description but not your comment.)

          Jesse Glick added a comment - BTW please use { code:none}…{code } in JIRA to make issues legible. (I could edit your description but not your comment.)

          Jesse Glick added a comment -

          Possibly related to ENTRYPOINT changes, would need to dig into it.

          Also BTW the Environment field in this issue includes everything but the most relevant bit: which version of this plugin you are running.

          Jesse Glick added a comment - Possibly related to ENTRYPOINT changes, would need to dig into it. Also BTW the Environment field in this issue includes everything but the most relevant bit: which version of this plugin you are running.
          Wilfried Goesgens made changes -
          Environment Original: Ubuntu 16.04, Docker version 1.12.1, build 23cf638, Jenkins 2.27 New: Ubuntu 16.04, Docker version 1.12.1, build 23cf638, Jenkins 2.27; CloudBees Docker Pipeline 1.9

          Wilfried Goesgens added a comment -

          ok, added. Isn't there a markdown plugin for jira available? I'm tired of learning stuff just because. The `Style` dropdown doesn't know about code sections.

          Wilfried Goesgens added a comment - ok, added. Isn't there a markdown plugin for jira available? I'm tired of learning stuff just because. The `Style` dropdown doesn't know about code sections.

            kufi Patrick Kaufmann
            dothebart Wilfried Goesgens
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: