my company now has CVS, Fisheye and JIRA and we want to migrate the whole CVS-Repo to Git.
How handles Fisheye/JIRA the existing commit-messages inside the Git-Repo?
Has someone a link to some tips for this kind for migration? Elsewise ill raise a new question.
When you add the new migrated repository it will be indexed by FishEye. Once that's done all the commits that mention JIRA issues will be visible in JIRA when viewing the associated issue, as they were for the CVS repository.
Any commands for smart commits won't be re-executed, as we don't process smart commits during the initial indexing of the repository. Depending on your migration strategy, they might be processed for commits added later on. To be sure they won't be processed, you might want to temporarily disable Smart commits, until the indexing is complete, and then re-enable them
Thanks Peter, thats what i was expecting :-) With your answer i found now the corresponding link: https://developer.atlassian.com/fecrudev/tutorials/fisheye-smart-commit-tutorial "Smart commit handlers are not invoked on the initial indexing of a repository, only on an incremental update."
...word of mouth, so by 2016, we were working with several other entities on campus to implement Jira Service Desk . The Atlassian motto of “for every team” has really come true for us in this case. We...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot