Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Docker plugin fail task but avoid plugin exception Edited

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

1 answer

0 votes

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.

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.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bamboo

Bamboo 101 Video

G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...

190 views 4 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you