How do I upload an iterative pre-commit patch to Crucible?

[Doug Konrad]

How do I upload an iterative pre-commit patch to Crucible? The instructions (https://confluence.atlassian.com/display/CRUCIBLE/Iterative+reviews?continue=https%3A%2F%2Fconfluence.atlassian.com%2Fdisplay%2FCRUCIBLE%2FIterative%2Breviews&application=cac#Iterativereviews-Iterativepatchuploads) do not describe how to select the patch that the new patch is a revision of. I am getting anchoring failures.

[Doug Konrad · Accepted solution]

Thanks, Dave. Your answer lead me to consider if I was following the instructions exactly.

I was using Mercurial. Because it is a distributed RCS, I didn't take pre-commit literally. I was interpreting it as pre-push. As a result, I was generating a diff from a commit that was not yet in the repo that fisheye was monitoring. And because of that, I wasn't being presented with the dialogue to select the original patch.

I compared the diff headers between "hg diff >patch" and "hg diff -r XXXX -r YYYY >patch" and found the problem. Crucible is expecting -r YYYY in the header, but my command puts -r XXXX r YYYY which confused it. When I hand-edited the patch file to remove -r XXXX, leaving only -r YYYY, it worked.

In summary, if it looks like this:

diff -r f4142f6a05cf -r 6a78d9e66478 CmnClient/src/CmnClient/SystemManagerClient.cpp

It should be changed to look like this:

diff -r f4142f6a05cf CmnClient/src/CmnClient/SystemManagerClient.cpp

[davelahn]

Hi Doug,

When you uploaded the first patch, did it correctly anchor to the repository? If it does, when you add the iteration of that patch, it should show up (as per the screenshot in the doc you linked), allowing you to select it as an iteration of that previous patch.

Can you confirm that you've created your patches as per these instructions?

Best regards,

Dave Lahn