Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,361,397
Community Members
 
Community Events
168
Community Groups

Saving build log doesn't save entire log

Edited

I'm succesfully saving the build log using the `wget` version of the `curl` example [here](https://confluence.atlassian.com/bamkb/how-to-save-a-build-log-as-an-artifact-892498832.html)

And it works. But,

the saved log doesn't contain the entire log. Ok, so I'm aware that it won't save the very end of the log since after the finale stage (i.e. the saving stage) artifact are being stored and that produces some log. Thing is, the log I'm saving isn't saving more than like two stages before the final stage is called. That's where my log ends.

I've tried delaying using `sleep` `timeout` and `ping` up to 30s without any improvement to the content of my saved log.

___________________________ 

REPHRASING:

Tried saving the build log using:

wget -O my_build_log.txt --user=myuser --password=mypassword http://bambooserver/download/${bamboo.buildKey}/build_logs/${bamboo.buildResultKey}.log

and it works, but it does not save the log produced up until the wget-call is executed... it saves the log from a while before the call.
I've tried adding

sleep
timeout
ping

to delay the call to wget up to 60s.. doesn't help.

 

 

___________________________

Question 1: Is there a better way to save the log (so that I at least get log text up to where the saving stage takes place)?

 

Question 2: What is like the "refresh rate" of the log by Bamboo? Because it seems to update the log in intervals, but I don't know if it's time dependant or task dependant

1 answer

1 accepted

1 vote
Answer accepted

Hi Nima,

Thanks for reaching out to the Atlassian Community today! Please allow me to address your questions inline, below.

Question 1: Is there a better way to save the log (so that I at least get log text up to where the saving stage takes place)? 

Unfortunately this is currently the only known way of retrieving the logs while the build is running. The logs are streamed over the Java Message Service, and they are passed via a buffer, which does take some time to show. The only alternative would be to access the logs from the filesystem, but these would be the same as those we retrieve using cURL or wget. 

Question 2: What is like the "refresh rate" of the log by Bamboo? Because it seems to update the log in intervals, but I don't know if it's time dependant or task dependant

The log is technically refreshed every second, however, data that is in the buffer may not show right away. The log is indeed updated in intervals, but the interval is based on the buffer. 

If possible, could you please try with a longer sleep command, maybe in a task of its own? 

If you have any other questions, please don't hesitate to reach out!

Thanks,

Elias | Bamboo Support

Thank you for your answer.

The extra delay doesn't seem to help enough, and adding even more delay is not pretty :)

As a workaround, I'm going to create a separate plan as a final stage which collects all logs from relevant plans.

Suggest an answer

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

Bamboo 9.0 is now available

Hey there, Data Center community! I'm Martyna Wojtas and I am the Product Manager for Bamboo Data Center. I’m excited to share that Bamboo 9.0 is now available. We purpose-built this platform to help...

313 views 0 7
Read article

Atlassian Community Events