Currently bamboo uses the time stamp of the last build to detect changes. If the bamboo server clock is out of sync with the perforce server clock, then bamboo can easily miss changes and not trigger builds if there are changes.
Therefore, bamboo needs to change the way it detects changes.
[BAM-1096] Change the way bamboo detects changes in perforce
Workflow | Original: Bamboo Workflow 2016 v1 - Restricted [ 1433969 ] | New: JAC Bug Workflow v3 [ 3379109 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Bamboo Workflow 2016 v1 [ 1407649 ] | New: Bamboo Workflow 2016 v1 - Restricted [ 1433969 ] |
Workflow | Original: Bamboo Workflow 2014 v2 [ 608562 ] | New: Bamboo Workflow 2016 v1 [ 1407649 ] |
Workflow | Original: Bamboo Workflow 2014 [ 597879 ] | New: Bamboo Workflow 2014 v2 [ 608562 ] |
Workflow | Original: Bamboo Workflow 2010 [ 204115 ] | New: Bamboo Workflow 2014 [ 597879 ] |
Workflow | Original: reviewflow [ 165283 ] | New: Bamboo Workflow 2010 [ 204115 ] |
Workflow | Original: jira [ 79401 ] | New: reviewflow [ 165283 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
Hi,
Bamboo has now been configured to use perforce change numbers rather than time stamps to detect changes. This should resolve any time based issues that were occuring.
These changes will be included in release 1.0.4 (to be released this week) .
Cheers
Brydie