[SCM-611] AccuRev - call replica sync before export

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.5
• Fix Version/s: 1.5
• Component/s: maven-scm-provider-accurev
• Assignee: Olivier Lamy
• Reporter: Grant Gardner
• Created: 26/Feb/11 22:46
• Updated: 28/Feb/11 17:18
• Resolved: 28/Feb/11 17:18

Description

When using the AccuRev 4.9 feature that allows export of a specific version (transaction id), this will fail if you are using a replica server where this transaction is not available.

This appears for me in theBamboo maven scm integration since Bamboo does its change detection against the AccuRev master server and passes the top transaction id to an agent which exports the code from an AccuRev replica.

Unfortunately there isn't a nice way to detect if you are using a replica, apart from seeing a warning message when you try to sync so fix is to just always call replica sync and ignore any errors.