Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Deleting large files from Git without breaking Jira and Crucible integrations

Paul O'Flynn December 18, 2014

So I've done the research on removing these big files from history but it of course involves re-writing history and thus re-writing commit IDs. If I were to push this new modified repo to BitBucket it would presumably break the "Commits" links in (on-premise) JIRA and (on-premise) Crucible. I don't suppose anyone has tried this before and has any suggestions? This is not an open-source project. Thanks.

1 answer

0 votes
Boris Berenberg
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 18, 2014

For JIRA, all linking is done based on Issue Keys in Commit Messages. So everything should actually work just fine. I am not sure about Crucible. 

Paul O'Flynn December 19, 2014

Are you sure about that? I know it looks at the commit message for the Jira ID but I assume it does that only as new commits come in and forever more after that it links the two in a more direct manner. If it was always only using the commit msg then Jira would have to scan every commit msg in the repo every time a Jira ticket was opened for viewing. Thanks for the reply BTW.

Boris Berenberg
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 22, 2014

What you will need to do in JIRA is disable smart commits, then go to manage the repos in your DVCS plugin page, then Shift+Click on the Refresh repo icon, and do a Full refresh. Then you can re-enable smart commits. But yeah, everything will just be re-indexed based on the commit messages. I spoke with the Crucible team, and they said they would expect all of the "new" commits to get picked up as new commits, not replaced on the old ones. Do you have https://confluence.atlassian.com/display/CRUCIBLE/Storing+all+revisions+under+review enabled?

Paul O'Flynn December 22, 2014

Great, thx for the very informative answer. Regarding Crucible, if we turned this on would the new commit IDs (from old commits) _not_ be picked up and the review content still visible? TIA

Boris Berenberg
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 22, 2014

The old reviews should be orphaned basically with diffs in them but no commits. I would highly recommend testing this in a staging environment to be sure how it will work with your exact dataset and config.

Paul O'Flynn December 22, 2014

Cool, thanks man.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events