On Wed, Feb 7, 2018 at 2:43 PM, niristotle okram <[email protected]> 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 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 steps inside that container. The workspace is mounted read-write > into the container. * > > Did you checked if the workspace have the file? > > A really brut way, if you want to really shell into the container, might > be to docker run the same image, in the workspace mnaually and try to > trigger the steps manually. Else, use try and catch to not keep the > container enaged even if the main execution fails. > But I can't really reproduce the Jenkins run-time though. I'm really surprised you can't pause the build or have a flag that says don't kill the container at the end of the build. This should really be a feature for docker based builds. -aps -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPpy_fGNZ90Wa9nOx6n3h2m6N0bsvpCjHhaH0vqdyaHVcM3SBQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
