Hi,

We have changed the way bamboo detects perforce changes to use the change numbers rather than the time stamp. Hopefully this should solve all these problems.

The changes will be included in the next release (coming soon).

Cheers
Brydie

Hi,

It seems that occasionally Bamboo will sync the repository but then will fail to trigger a build. This happens when the bamboo server clock and the perforce server clock are out of sync. Even th smallest difference can cause this effect. This behaviour sounds like what you are experiencing.

Let me know if this may be the cause of your issues.

If this is the problem, we are currently looking at changing the way bamboo detects perforce changes to not rely on the time.
You can track this issue here: http://jira.atlassian.com/browse/BAM-1096

Cheers
Brydie

I've seen Perforce changes go "missing" here. The log shows the working copy being updated by p4, but no build triggers.

I haven't established a common cause for this from my observations.

This is happening again - and I think I see the pattern.

If the time between manual builds is too small - the changes are not picked up. I waited 15 hours, submitted a change, did a manual build - the change was displayed.

Then I submitted another change, did another manual build - the change was not picked up.

Glad it's working again!

Now it is working again! I'm not sure why it wasn't working before. I guess you can close this issue.

Hm - seems the changes are not displayed for scheduled builds either. I thought this was working before.