Re: How to keep a running docker container after a build fails?

On Tue, Feb 13, 2018 at 7:56 AM, Reinhold Füreder wrote: > Hi aps, > > > > Just in case the problem is still there and to avoid a misunderstanding: > > > > Based on (a) Victor’s hint “tr[y] with the docker.inside syntax […] It > might give you the chance to debug it

RE: How to keep a running docker container after a build fails?

Hi aps, Just in case the problem is still there and to avoid a misunderstanding: Based on (a) Victor’s hint “tr[y] with the docker.inside syntax […] It might give you the chance to debug it somehow.” and (b) your own comment “I'm really surprised you can't pause the build”:

Re: How to keep a running docker container after a build fails?

As you mentioned the lifecycle of the docker container with the step 'withDockerContainer' is well defined and doesn't allow to keep it alive. So i was assuming the docker.inside might help you to keep the container alive, but I was wrong: the docker.inside step removes the container while the

Re: How to keep a running docker container after a build fails?

On Thursday, February 8, 2018 at 5:37:05 AM UTC-5, Victor Martinez wrote: > > Just an idea, you have tried with the docker.inside syntax? ( > https://jenkins.io/doc/book/pipeline/docker/#running-sidecar-containers) > It might give you the chance to debug it somehow. > > What's the difference

Re: How to keep a running docker container after a build fails?

Just an idea, you have tried with the docker.inside syntax? (https://jenkins.io/doc/book/pipeline/docker/#running-sidecar-containers) It might give you the chance to debug it somehow. Cheers -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group.

Re: How to keep a running docker container after a build fails?

Pausing a build comes with an expense of a busy executor. Why not file a JIRA ticket to the plugin folks, might help someone someday. On Wed, Feb 7, 2018 at 1:47 PM, pisymbol . wrote: > > > On Wed, Feb 7, 2018 at 2:43 PM, niristotle okram > wrote: >

Re: How to keep a running docker container after a build fails?

On Wed, Feb 7, 2018 at 2:43 PM, niristotle okram wrote: > for debugging, > why not put some more echo/ls commands to check if the file you are > looking is there or not from the container. > Sure, but it takes 30+ minutes just to get to this spot. > > The documentation

Re: How to keep a running docker container after a build fails?

for debugging, why not put some more echo/ls commands to check if the file you are looking is there or not from the container. The documentation says: *Takes an image ID or symbolic name which must already have been pulled locally and starts a container based on that image. Runs all nested sh

Re: How to keep a running docker container after a build fails?

On Monday, February 5, 2018 at 3:16:04 PM UTC-5, pisymbol wrote: > > withDockerContainer(image: "centos:7", args: "--privileged") { > stage ('Negotiate World Peace') {} > stage ("Cure Cancer") {} > > Anyone do this? I mean how does one debug build bugs in a docker

Re: How to keep a running docker container after a build fails?

withDockerContainer(image: "centos:7", args: "--privileged") { stage ('Negotiate World Peace') {} stage ("Cure Cancer") {} etc. -aps -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and

Re: How to keep a running docker container after a build fails?

Hi, How do you launch your builds? Pipeline/Freestyle? Cheers -- 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.

How to keep a running docker container after a build fails?

I have Googled this and still can't find as simple answer. Is there a way to have Jenkins not clean up the container after a build? I am having a build failure and I don't quite understand why (a file doesn't exist when it should). But I have to replay the entire build which takes about 40