Repository sync time

[Martin Bayreuther]

Hello all,

we are currently looking into a code review solution using crucible. For that we create review requests automatically when code is submitted. The problem we run into is as follows.

• Code is submitted (at time 0:00)
• Review request in Crucible is created (at time 0:01)

By the time the review is created, crucible is not yet aware of the change (due to the polling nature of the repository link). We have reduced the polling interval to 60 seconds but still our typical submit scenario takes 1 min. 30 seconds as we have to do something like this

• Code is submitted (at time 0:00)
• Wait loop until change is visible in crucible (anywhere from 0:10 to 1:30)
• Review request in Crucible is created (anywhere from 0:20 to 1:40)

Is there a programmatic way to tell crucible about a submit and run the changeset collector on demand?

Best regards

Maba

[Conor · Accepted solution]

You can ask Fisheye/Crucible to perform an incremental scan using the scannow command line option

http://confluence.atlassian.com/display/FISHEYE/Command-Line+Options

If you use the -s flag the command will only return once the scan has completed.

[Martin Bayreuther]

Hello Conor,

this would be working locally. The submit and the request for review generation are done on the users development machine. So he does a svn commit which at the same time triggers the review request. So something that works remotely via the REST interface is needed.

Best regards

Maba

[Conor]

It would be possible to use the Smart Commits feature (in 2.7) to have Crucible automatically create the review when it processes the commit (see http://confluence.atlassian.com/display/FISHEYE/Using+Smart+Commits)

[Martin Bayreuther]

The second comment from Conor is the key.