Docker plugin fail task but avoid plugin exception

[Chris Mitchell]

I currently use docker plugin as part of my build process in bamboo.

When the executable called by the docker plugin exits with a non-zero status, the docker plugin throws an exception. This means the end of the build logs contain the irrelevant docker plugin stack trace rather than the important detail of what has failed ie the output from the task run within the docker plugin

All of our builds are returning some status like "Error occurred while running Task 'Deploy(5)' of type com.atlassian.bamboo.plugins.bamboo-docker-plugin:task.docker.cli."

Is there some way to control the output of the docker plugin easily that would prevent the stack trace output?

Is there an approach that tasks within docker plugin should take to signal outcome (success or failure & reason)?

I tried to include an example of the stack trace i want to get rid of but apparently that was enough to get marked as spam

[Daniel Santos]

Hi @Chris Mitchell

I just ran some tests locally and was able to reproduce the scenario you've experienced. I even found an improvement request about it in our issue tracker.

• [BAM-18745] Can't see docker command errors when use Docker task
  
  

Is there some way to control the output of the docker plugin easily that would prevent the stack trace output?

Not if you keep using the Docker task. 

Is there an approach that tasks within docker plugin should take to signal outcome (success or failure & reason)?

Maybe if you use a script and treat the errors, but that doesn't sound like a good plan.

Moving forward

I see two options to overcome this issue:

• Adjust your build to use Docker Runner instead.
  It will return the error from the commands run, not from Docker itself.
• Use a script task with docker commands instead of the docker task.

I hope that allows you to move forward.