Thanks for trying out Bamboo 0.6.

We have had another report of this issue coming in. (see BAM-399).

We are looking at it and hope to get to the bottom of this shortly.

Regards,
Edwin

As mentioned in BAM-399, this seems to be a problem with one of Bamboo's dependencies which is loading an old version of the xml parser.

For a temporary workaround while we fix this, could you please try removing the xerces-1.2.3.jar from the webapp/WEB-INF/lib folder where you have installed Bamboo.

I don't think the reason why the check in comments are not appearing. I think that's a separate issue we'll look into.

Thanks for reporting,

cheers

Ben

You can try the workaround above or download 0.6.2 shortly on the Bamboo page at http://confluence.atlassian.com/display/BAMBOO/Download

Could you please let me know if your still having problems in regards to the status of the check-in comments from Perforce.

Cheers

Ben

I installed the 0.6.2 release and tried it again. I was able to successfully configure and test my JIRA server. However, I'm still not seeing the Perforce check-in comments, so I can't see the JIRA issue I referenced.

I agree that this is a different problem. I attached my log file again. If you look at line 1932, you'll see this:
2006-11-09 09:40:51,046 INFO [output stream pumper] [StreamToListPumper] [PROJA] //depot/main/src/My.java#5 - updating c:\p4local.ws\depot\main\src\My.java
2006-11-09 09:40:51,156 INFO [BAM::BuildChangeDetector] [Command] err>Unknown command. Try 'p4 help' for info.
2006-11-09 09:40:51,156 INFO [BAM::BuildChangeDetector] [AbstractBuildStrategy] project A has 1 changes.

It looks like the p4 client did not understand one of the commands that Bamboo issues. Its odd, since obviously the rest of the P4 interaction (to sync the workspace) is working. I assume you're just using 'p4 changes' to get the list of files that have changed. I'm using the 2006.1 version of P4 (Rev. P4/NTX86/2006.1.BETA/101179 (2006/06/07)), but a basic command like 'changes' doesn't change very often.

Also, on line 1957, you'll see a large stack trace that happened when I clicked on the 'code changes' link for my latest build. I'm not sure if this is related to the P4 error.

I'm not sure if you want me to open another issue for this.

Cheers,
Randy

2006-11-09 10:00:51,140 DEBUG [BAM::BuildChangeDetector] [Command] C:\Program Files\Perforce\p4.EXE -u rdefauw -p 1666 -c local.ws sync //local.ws/depot/main/...
2006-11-09 10:00:51,203 INFO [output stream pumper] [StreamToListPumper] [PROJA] //depot/main/src/My.java#6 - updating c:\p4\local.ws\depot\main\src\My.java
2006-11-09 10:00:51,203 DEBUG [BAM::BuildChangeDetector] [Command] working directory = null
2006-11-09 10:00:51,203 DEBUG [BAM::BuildChangeDetector] [Command] C:\Program Files\Perforce\p4.EXE -p 1666 -c local.ws changes -s submitted //local.ws/depot/main/...@2006/11/09:09:40:51,2006/11/09:10:00:51
2006-11-09 10:00:51,250 DEBUG [BAM::BuildChangeDetector] [Command] working directory = null
2006-11-09 10:00:51,250 DEBUG [BAM::BuildChangeDetector] [Command] C:\Program Files\Perforce\p4.EXE -p 1666 -c local.ws getPrettyPrint -s 10
2006-11-09 10:00:51,281 INFO [BAM::BuildChangeDetector] [Command] err>Unknown command. Try 'p4 help' for info.

So after the sync picks up a new file, it asks for the submitted changes, which is fine. I think it detected that change list #10 was the one that caused the build. But the next p4 command is kind of strange:
p4 getPrettyPrint -s 10
There's no p4 command called 'getPrettyPrint'.

Cheers,
Randy

I'll look into this a bit further. I've updated the issue to reflect your actual issue.

Cheers

Mark C

Looking through the code, it looks like we were trying to get the change list details through the use of the getPrettyPrint command... From the P4 reference, it looks as though the command should really be describe.

Could your try running on the command line:

C:\Program Files\Perforce\p4.EXE -p 1666 -c local.ws describe -s 10

and pasting the exact output of it back into the issue? This might be the command we're looking for.

Cheers,

Mark C

Yes, the 'describe' command is probably what you're looking for. Here's the output:
C:\p4\local.ws2\depot\main>p4 describe -s 10
Change 10 by rdefauw@local.ws2 on 2006/11/09 09:59:22

another test

Affected files ...

... //depot/main/src/My.java#6 edit

If you're just looking for check-in comments, the 'changes -l' command will work, although it doesn't have the file list.

Thanks for this info. We'll try to get up a patch for you to try.

Cheers,

Mark C

Sorry but unfortunately I was unable to look into getting this fixed today. Hopefully we'll have something early next week.

Regards

Ben

Thanks for the feedback. The bug has been fixed for 0.7 but unfortunately we won't be issuing a patch for this for the 0.6.x releases as there are a few flow on effects that needs to be addressed.

Cheers

Ben