History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: BAM-1030
Type: Improvement Improvement
Status: Closed Closed
Resolution: Duplicate
Priority: Major Major
Assignee: Brydie McCoy [Atlassian]
Reporter: Paul Smith
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Bamboo

Ability to download particular build log file

Created: 14/Mar/07 06:57 PM   Updated: 02/Jul/07 11:24 PM
Component/s: Build Process
Affects Version/s: 1.0
Fix Version/s: 1.2

Time Tracking:
Not Specified

Issue Links:
Duplicate
 

Participants: Brydie McCoy [Atlassian], Edwin Wong [Atlassian] and Paul Smith
Since last comment: 68 weeks, 2 days ago
Number of comments: 3
Labels:


 Description  « Hide
Our build and unit test process ends up generating a huge gob of logging info. When I try to view a failed builds log file in bamboo, Firefox on the Mac at least tends to hang while it tries to render this.

I would really like to have a link that I could click on that allows me to download the builds log file to a local plain text (no HTML thanks) log file file for further analysis.

Even better, if there was some way to mark in the build log info for a given failing unit test what the System.out and System.err looked like while that build was running.

I would count this as pretty important (for me! ) as I'm finding it very hard to see what exactly is going on with some of our unit tests when running in Bamboo.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Edwin Wong [Atlassian] - 18/Mar/07 07:44 PM
Paul,

Thanks for the comments/suggestion about the logs.

With regards to the unit test failures, I believe the logs are attached for failed builds if you click to the tests tab within a build?

Regards,
Edwin


Paul Smith - 18/Mar/07 07:48 PM
Yes, you do get access to the message of the failing test, but that's not the same as the system out during the entire test run. Some tests fail because of particular cases, and it's not always possible to see exactly from the test case failure output exactly WHY it was failing. Often that information might be in previous logging statements.

Unless I'm missing a link somewhere.


Paul Smith - 29/Mar/07 10:17 PM
I think this is a duplicate of BAM-859