Bamboo checkout from repository - where are the logs?

When we do a build in Bamboo, we see in the logs that the build started:

simple	05-Jul-2011 14:50:03	Executing build ABC-ABCPLAN-1047
simple	05-Jul-2011 14:50:03	Running pre-build action: VCS Version Collector
simple	05-Jul-2011 14:50:03	Running pre-build action: Build Number Stamper
simple	05-Jul-2011 14:50:03	Running pre-build action: Pre Command Agent Runner
simple	05-Jul-2011 14:50:03	Building started with ScriptBuilder

And in the build summary there is text that says "Build took 20 minutes". If I mouse over that text, it tells me in a popup box
that "source updating for 8 minutes"

What I want to see is the LOG of the source updating. Is that not logged? Is it hidden somwehere?
Is there a configuration setting somewhere that controls whether this is logged or not?

I checked the docs and the forums, can't find it if it's there.

Currently Bamboo 2.5, but I also don't see this in documentation for 3.1

3 answers

0 votes

It's not logged. Depending on your VCS, you may be able to switch detailed logging on.

We use subversion. I looked at the bamboo admin panel for logging, didn't see anything that was (obviously) VCS or SVN related.

We use Subversion as well and have managed to get the results of the update of the repository by doing the following.

In the Administration menu, enter the 'Log Settings' under 'System'. This gives you a selection of results to log, if you set 'Webwork' and 'root' to 'debug' verbosity this logs everything that occurs.

Which version of Bamboo are you referencing? I am using Bamboo 2.3.1 and I don't see:

In the Administration menu, enter the 'Log Settings' under 'System'.

I'm using 3.1.4 and its located right where he said it was, here's the URI:
https://bambooServerFQDN/admin/configLog4j.action

This feature was introduced in 2.4, that's why you can't find it.

Thanks. Must be a new feature in the newer versions of Bamboo.

https://bambooServerFQDN/admin/configLog4j.action... that's your internal sever, on one can get to that. :)

actually, its not my internal server, look at the servername... its a stub.. like saying https://someDudesWebServerFQDN

the URI (the part that is AFTER the server FQDN) was there so you could try to access it on your server by supplimenting the stub with your server's FullyQualifiedDomainName (FQDN).. but as Bruski clarified, its introduced in a newer version than you have. Good luck.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Monday in Jira Ops

Jira Ops Early Access Program Update #1: Announcing our next feature and a new integration

Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...

507 views 0 9
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you