nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Crucible tried to anchor your patch, but did not find any matching paths --- mercurial

Mohammed Mohamm3

I am using mercurial to create a patch and upload it to crucible, however it cannot anchor no matter what I try. I've tried creating the patch exactly how the atlassian website says by using

hg diff &gt; patch

However, when I upload the result, it does not anchor, even if I pick the repository manually from the drop down.

I have the repo cloned with the new files added, but not committed. The diff looks correct, but there must be something wrong to throw off the anchoring. I just want to be able to see iterative changes to the patches.

Any help is appreciated. Thanks

Accepted answers

All comments

gustavo_refosco

Hi Mohammed,

As you mentioned you are creating a patch for new files, not yet commited (i.e. not still indexed), it's expected Crucible won't be able to anchor this patch to the repository. In this case, the patches would be uploaded separately, as stated by the document with "If Crucible is unable to anchor the patch to a repository, you will only be able to upload the patches as separate files".

It's still possible, though, to perform iterative patch reviews even not being able to attach these patches to the repository. You can do this adding the patches as attachments, as follows:

Create a review and, when adding content, select Attachments.
In the next screen, click in Upload another file as the base of a diff, then for *Base of Diff File select the file correspondent to the first revision.
For File select the file correspondent to the next revision, which will be compared to the previous one.
Click in Upload. This will upload the two files, diffing them.

Regards,

Gustavo Refosco

Mohammed Mohamm3

This results in a diff file being uploaded as an attachment without creating the directory tree with each separate file. Any ideas?

Mohammed Mohamm3

My patch consists of multiple files.

gustavo_refosco

Hi Mohammed,

In this case the only workaround I can think of is to review each file separately, uploading the first revision of this file (when it's created) to the review and, upon any changes, upload it again, with the same filename, so the diff will be done. This could be done, for each file, as follows (this is just an example of workflow):

Create a new file (e.g. test.txt).
Create a review, adding this test.txt as an attachment.
After the file is reviewed, apply the necessary modifications to the file in the repository, then upload it as an attachment with the same filename.
Refresh the page. You'll see this addition revision will be shown in the review, to be diff against the previous one.

I'm aware this may not be the most ideal solution. In case you have any thoughts on your mind and would like to share a suggestion please feel free to raise a feature request at https://jira.atlassian.com.

Regards,

Gustavo Refosco

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

fisheye-crucible

fisheye-crucible-administration