[JIRA] (JENKINS-39307) pipeline docker execution aborts without reason
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-39307 pipeline docker execution aborts without reason Change By: Vivek Pandey Labels: diagnostics docker triaged-2018-11 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-39307) pipeline docker execution aborts without reason
Title: Message Title Wilfried Goesgens commented on JENKINS-39307 Re: pipeline docker execution aborts without reason As discussed on IRC so its not lost - stat'ing the /proc/ directory should be as portable and reduce the need for the ps command. It should also be faster, since [ -d /proc/] can be done as shell internal and doesn't need to fork a ps command. Another cure would be to add a counter to the ps calls, and if that was just one attempt, and docker shut down finds running processes in this container, add a warning to the error message - whether ps is available in the container or not. 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-39307) pipeline docker execution aborts without reason
Title: Message Title Jesse Glick commented on JENKINS-39307 Re: pipeline docker execution aborts without reason Oh and no it should not be ps -o pid=7. ps -o pid= 7 is intentional. 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-39307) pipeline docker execution aborts without reason
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-39307 pipeline docker execution aborts without reason Change By: Jesse Glick Labels: diagnostics 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-39307) pipeline docker execution aborts without reason
Title: Message Title Jesse Glick commented on JENKINS-39307 Re: pipeline docker execution aborts without reason Yes you need at least cat and ps in the container. Currently the plugin does not try to verify these prerequisites or provide tailored error messages. 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-39307) pipeline docker execution aborts without reason
Title: Message Title
Wilfried Goesgens edited a comment on JENKINS-39307
Re: pipeline docker execution aborts without reason
It seems as if jenkins doesn't properly detect the PID of the process:It tries to build a commandline like that: [pid 6503] execve("/usr/bin/docker", ["docker", "exec", "e58e441dbf413c4180bca9f3e8db816eed1f3d985c21036fd93d9c970174141d", "env", "ps", "-o", "pid=", "7"], [/* 15 vars */] which will always produce an empty result, since it should be "pid=7" instead [edit]if ps is not installed in the container this will fail miserably.
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-39307) pipeline docker execution aborts without reason
Title: Message Title
Wilfried Goesgens commented on JENKINS-39307
Re: pipeline docker execution aborts without reason
It seems as if jenkins doesn't properly detect the PID of the process: It tries to build a commandline like that: [pid 6503] execve("/usr/bin/docker", ["docker", "exec", "e58e441dbf413c4180bca9f3e8db816eed1f3d985c21036fd93d9c970174141d", "env", "ps", "-o", "pid=", "7"], [/* 15 vars */] which will always produce an empty result, since it should be "pid=7" instead
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-39307) pipeline docker execution aborts without reason
Title: Message Title
Wilfried Goesgens edited a comment on JENKINS-39307
Re: pipeline docker execution aborts without reason
Ok, there is a workaround, but man thats hacky!One uses `nohup` to run the script itself, and after that make jenkins poll for the process still existing by examining the existence of its pid via the proc filesystem.{code:none} BUILDSCRIPT="nohup ${BUILDSCRIPT} 2 > &1 > nohup.out 2> & echo 1 & PID= \$! ; echo \$PID > pid; tail -f nohup.out & wait \$PID ; kill %2" try {if (VERBOSE) { print(BUILDSCRIPT)}sh BUILDSCRIPT } catch (err) {RUNNING_PID=readFile("pid").trim()def stillRunning=truewhile (stillRunning) { def processStat="" try{scripT="cat /proc/${RUNNING_PID}/stat 2>/dev/null"echo "script: ${scripT}"processStat = sh(returnStdout: true, script: scripT) } catch (x){} stillRunning=(processStat != "") sleep 5}sh "tail -n 100 nohup.out" }}{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-39307) pipeline docker execution aborts without reason
Title: Message Title
Wilfried Goesgens commented on JENKINS-39307
Re: pipeline docker execution aborts without reason
Ok, there is a workaround, but man thats hacky! One uses `nohup` to run the script itself, and after that make jenkins poll for the process still existing by examining the existence of its pid via the proc filesystem.
BUILDSCRIPT="nohup ${BUILDSCRIPT} 2>&1 > nohup.out & echo \$! > pid; tail -f nohup.out & wait; kill %2"
try {
if (VERBOSE) {
print(BUILDSCRIPT)
}
sh BUILDSCRIPT
}
catch (err) {
RUNNING_PID=readFile("pid").trim()
def stillRunning=true
while (stillRunning) {
def processStat=""
try{
scripT="cat /proc/${RUNNING_PID}/stat 2>/dev/null"
echo "script: ${scripT}"
processStat = sh(returnStdout: true, script: scripT)
}
catch (x){}
stillRunning=(processStat != "")
sleep 5
}
sh "tail -n 100 nohup.out"
}
}
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
[JIRA] (JENKINS-39307) pipeline docker execution aborts without reason
Title: Message Title Wilfried Goesgens commented on JENKINS-39307 Re: pipeline docker execution aborts without reason Some more testing, discussing with the fedora cloud team: https://github.com/fedora-cloud/docker-brew-fedora/issues/43 It seems that this behaviour was introduced with FC 21->22 - as one can quickly check by changing the ID in the docker container. 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-39307) pipeline docker execution aborts without reason
Title: Message Title Jesse Glick commented on JENKINS-39307 Re: pipeline docker execution aborts without reason the sh-step is not executed inside of the docker container Nor is it supposed to be. withRun merely starts a container, then stops it. Anything you want to do with that container should be done via the closure parameter. 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-39307) pipeline docker execution aborts without reason
Title: Message Title
Wilfried Goesgens commented on JENKINS-39307
Re: pipeline docker execution aborts without reason
The Sugested workaround:
stage("test") {
node("docker") {
docker.image("fedoratwentythree/build").withRun {c ->
sh "cat /etc/issue; while /bin/true; do echo 'x'; sleep 1; done"
}
}
}
will not terminate, but also won't work properly. the `/etc/issue` indicates that the `sh`-step is not executed inside of the docker container:
+ cat /etc/issue
Ubuntu 16.04.1 LTS \n \l
+ /bin/true
+ echo x
x
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-39307) pipeline docker execution aborts without reason
Title: Message Title Wilfried Goesgens commented on JENKINS-39307 Re: pipeline docker execution aborts without reason The first time I observed this behaviour was on Oct 12 and whatever the latest released jenkins/plugins was way back then. Meanwhile I also saw this happen at least once with an OpenSuSE 13.1 container. 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-39307) pipeline docker execution aborts without reason
Title: Message Title Wilfried Goesgens commented on JENKINS-39307 Re: pipeline docker execution aborts without reason 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. 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-39307) pipeline docker execution aborts without reason
Title: Message Title
Wilfried Goesgens edited a comment on JENKINS-39307
Re: pipeline docker execution aborts without reason
This pipeline script:{code:none}stage("test") {node("docker") {docker.image("fedora:23").inside {sh """while /bin/true; do echo "."; sleep 1; done"""}}}{code}results in this output:{code:none}[Pipeline] stage[Pipeline] { (test)[Pipeline] nodeRunning 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 PipelineERROR: script returned exit code -1Finished: FAILURE{code}while i.e. using the docker image 'ubuntu:16.04 will result in an endless continuing 'echo .' list. {quote}{{test}}{quote}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39307) pipeline docker execution aborts without reason
Title: Message Title
Wilfried Goesgens edited a comment on JENKINS-39307
Re: pipeline docker execution aborts without reason
This pipeline script:{code:none}stage("test") {node("docker") {docker.image("fedora:23").inside {sh """while /bin/true; do echo "."; sleep 1; done"""}}}{code}results in this output:{code:none}[Pipeline] stage[Pipeline] { (test)[Pipeline] nodeRunning 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 PipelineERROR: script returned exit code -1Finished: FAILURE{code}while i.e. using the docker image 'ubuntu:16.04 will result in an endless continuing 'echo .' list. {quote}{{test}}{quote}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39307) pipeline docker execution aborts without reason
Title: Message Title
Wilfried Goesgens edited a comment on JENKINS-39307
Re: pipeline docker execution aborts without reason
This pipeline script:{code:none}stage("test") {node("docker") {docker.image("fedora:23").inside {sh """while /bin/true; do echo "."; sleep 1; done"""}}}{code}results in this output: {code:none} [Pipeline] stage[Pipeline] { (test)[Pipeline] nodeRunning 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 PipelineERROR: script returned exit code -1Finished: FAILURE {code} while i.e. using the docker image 'ubuntu:16.04 will result in an endless continuing 'echo .' list.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39307) pipeline docker execution aborts without reason
Title: Message Title
Wilfried Goesgens edited a comment on JENKINS-39307
Re: pipeline docker execution aborts without reason
This pipeline script: {code:none} stage("test") {node("docker") {docker.image("fedora:23").inside {sh """while /bin/true; do echo "."; sleep 1; done"""}}} {code} results in this output:[Pipeline] stage[Pipeline] { (test)[Pipeline] nodeRunning 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 PipelineERROR: script returned exit code -1Finished: FAILUREwhile i.e. using the docker image 'ubuntu:16.04 will result in an endless continuing 'echo .' list.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39307) pipeline docker execution aborts without reason
Title: Message Title Wilfried Goesgens updated an issue Jenkins / JENKINS-39307 pipeline docker execution aborts without reason Change By: Wilfried Goesgens Environment: Ubuntu 16.04, Docker version 1.12.1, build 23cf638, Jenkins 2.27 ; CloudBees Docker Pipeline 1.9 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-39307) pipeline docker execution aborts without reason
Title: Message Title Jesse Glick commented on JENKINS-39307 Re: pipeline docker execution aborts without reason 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. 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-39307) pipeline docker execution aborts without reason
Title: Message Title
Jesse Glick commented on JENKINS-39307
Re: pipeline docker execution aborts without reason
BTW please use {code:none}…{code} in JIRA to make issues legible. (I could edit your description but not your comment.)
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-39307) pipeline docker execution aborts without reason
Title: Message Title
Wilfried Goesgens commented on JENKINS-39307
Re: pipeline docker execution aborts without reason
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.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
[JIRA] (JENKINS-39307) pipeline docker execution aborts without reason
Title: Message Title Jesse Glick commented on JENKINS-39307 Re: pipeline docker execution aborts without reason Steps to reproduce from scratch in a minimal, self-contained test case, please. 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-39307) pipeline docker execution aborts without reason
Title: Message Title
Jesse Glick updated an issue
Jenkins / JENKINS-39307
pipeline docker execution aborts without reason
Change By:
Jesse Glick
I'm trying to compile ArangoDB in one of these docker containers:https://github.com/arangodb-helper/build-docker-containers/tree/master/distrosIt 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.04The 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 deprecatedEntering stage Send Notification for buildProceeding[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.
[JIRA] (JENKINS-39307) pipeline docker execution aborts without reason
Title: Message Title
Wilfried Goesgens updated an issue
Jenkins / JENKINS-39307
pipeline docker execution aborts without reason
Change By:
Wilfried Goesgens
I'm trying to compile ArangoDB in one of these docker containers:https://github.com/arangodb-helper/build-docker-containers/tree/master/distrosIt 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.04The 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 deprecatedEntering stage Send Notification for buildProceeding[Pipeline] mailIn 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.
[JIRA] (JENKINS-39307) pipeline docker execution aborts without reason
Title: Message Title
Wilfried Goesgens updated an issue
Jenkins / JENKINS-39307
pipeline docker execution aborts without reason
Change By:
Wilfried Goesgens
I'm trying to compile ArangoDB in one of these docker containers:https://github.com/arangodb-helper/build-docker-containers/tree/master/distrosIt 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.04The 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 deprecatedEntering stage Send Notification for buildProceeding[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.
[JIRA] (JENKINS-39307) pipeline docker execution aborts without reason
Title: Message Title Wilfried Goesgens created an issue Jenkins / JENKINS-39307 pipeline docker execution aborts without reason Issue Type: Bug Assignee: Unassigned Components: docker-workflow-plugin Created: 2016/Oct/27 11:22 AM Environment: Ubuntu 16.04, Docker version 1.12.1, build 23cf638, Jenkins 2.27 Priority: Minor Reporter: Wilfried Goesgens 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]
