We recently started using Atlassian products (JIRA / Fisheye / Crucible / SVN) and the move over in our development process was fairly simple with the exception of SVN as we prefer Git / Mercurial repositories. When FishEye OnDemand starts supporting Mercurial or Git, we'd like to look at moving back to one of these systems. Is there currently a migration path planned, or will it be equivalent to setting up a new repository?
Please read the following important announcement:
Please direct your questions to this question:
Subversion, FishEye/Crucible (the Source + Review Bundle) on OnDemand End of Service
There isn't an official date set when FishEye OnDemand will support Mercurial and Git, however the latest downloadable version of FishEye now supports Git and Mercurial so once our developers have overcome the challenges of bundling the latest version then native Git and Mercurial support will be available on the OnDemand platform.
The reason it isn't already available is because the OnDemand platform relies on substantial customisations in order to allow the "a la carte" offering where different customers can have wildly different configurations based on their needs. However, as I'm sure you can appreciate, the number one priority is to provide a stable and secure platform so the latest version of FishEye, (with native Git and Mercurial support), will be available on the OnDemand platform as soon as we're able to provide it to our customers in a stable and secure manner...and, most importantly, in a manner that won't negatively impact our current FishEye OnDemand customers.
We are aware that many of our customers require Mercurial/Git before even considering migration to the OnDemand platform, but it's more important for Atlassian to get it right, even if that means some delays, rather than to rush it and get it wrong, (which could cause all manner of issues for our customers and severely disappoint those customers who have been eagerly waiting that functionality).
Therefore, I hope you understand the reasons why it isn't yet available and you are reassured that we are working on providing this functionality with the highest priority, even though I can't currently tell you when it will be available.
All the best,
John, just to be clear, you're talking about native Git and Mercurial support in FishEye OnDemand, right? When can we expect to see Git support for private Bitbucket/Github repos? We're already using Bitbucket and probably wouldn't have a good reason to switch to this upcoming native Git support.
Thanks for the information John. From all I've seen and some of the other questions I figured that Mercurial / Git support was coming at some point and was more interested in the migration path. We'd rather not lose the history we've got now in the SVN system, and were hoping that when Mercurial support was added that we'd be able to transition to Mercurial again without losing the history we've got in SVN. Do you know if there is a plan for this (even if the plan is that we'd keep both up and only use the SVN repository to view history)?
@Joel: I can confirm that I am referring to the same native support for Git and Mercurial that we have in the downloadable versions of our products. However, as I have already mentioned, there are a number of challenges involved in porting applications over to the OnDemand platform so until it is released I can't make any promises about the exact functionality that will be available.
@Jan: I'm sorry to say that I don't know exactly what is planned by our developers, however I'm sure they will endevaour to provide some functionality to make migration as painless as possible for our customers if they can.
We're looking at Jira at the moment, and the lack of FishEye OnDemand for Mercurial is a real pain. It's making it very hard to recommend this solution over Fogbugz/Kiln. We really don't want to have to continue using Subversion. A target date for Mercurial (or even Git) support would be hugely helpful in coming up with a recommendation
Mercurial is critical to our using On Demand. We are NOT switching back to SVN. IMO, supporting Mercurial (or atleast GIT, which is compatible) should be a top priority concidering how many developers use thes applications and that JIRA, FishEye/Crucible, etc already support Mercurial now (standalone version).
I have seen these tickets - they have been ongoing for some time.
What I am looking for is fairly straightforward. I want to host my Git repositories in BitBucket. I want to use FishEye/Crucible for code review in an OnDemand environment.
I get the impression this is planned. There must be some timeframe, even a ball park figure. This Year? Q1 next year? Any indication at all?
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Planning and grooming sessions all come with their own sets of rules. Team members meet to estimate stories or other work items, all according to an agreed-upon process. And with every session comes ...
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