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.
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.
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?
Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs