|
If you were logged in you would be able to see more operations.
|
|
|
Although Bamboo has detected changes in our Perforce repository, it doesn't appear to care. It sync's the files to the local client workspace, but does not kick off the Ant build. I've attached a screen shot of the activity view for our test project.
This may be related to BAM-747, though we are no experiencing any of the Hibernate issues that ticket describes.
|
|
Description
|
Although Bamboo has detected changes in our Perforce repository, it doesn't appear to care. It sync's the files to the local client workspace, but does not kick off the Ant build. I've attached a screen shot of the activity view for our test project.
This may be related to BAM-747, though we are no experiencing any of the Hibernate issues that ticket describes. |
Show » |
|
Bug
Resolved
Major
Perforce modifications not causing build
Sorry for the inconvenience caused.
We have seen this issue a few times. We believe this is caused by Bamboo detecting Perforce changes by using timestamps rather than build numbers. (Please see
BAM-1096). We have fixed this issue, which will be available shortly in the next point release (1.0.4) available later this week.Cheers,
Ajay