Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Bamboo Deployment output/log tail empty

Hi there,

I have recently updated Bamboo 6.9.2

We run deployment tasks and watch the tail of the logs to review progress.  Since the upgrade, the logs have flashed from the tail, to reporting that there's no log output, back to tail and then empty again.

Once the deployment is complete, the log is correctly displayed.  Has anyone experienced this?  Is there an explanation/solution ?

1 answer

0 votes
Victor Debone
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 20, 2019

Hello @Amanda Culver :)

Do you have any error or exception being thrown on the log of Bamboo Server? When you mention 'tail', what exactly part of Bamboo are you referring to?

Also, what was the previous version of Bamboo you've updated from? I assume the experience on deployment tasks back on this version was different?

As a deployment runs, the most recent ~20 lines of the tail of the log file appears on the landing page - real time.


My problem was that it would

loop :

            Declare the log empty

            wait many seconds, 

            produce some output,

until deployment complete

produce the correct log file in the 'log' tab.

subsequent to this, I bounced the server and the log is now producing expected output.  It seems that this is indicative of the server under pressure.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events