See ticket https://jira.reactos.org/browse/ONLINE-731. But for any integration except FishEye we must convert our other repos to Git, because there are no real alternatives to FishEye for SVN.
2017-10-14 19:29 GMT+03:00 Mark Jansen <mark.jan...@reactos.org>: > Hey, > > Well as far as I know, the only use we had for FishEye were code reviews > and smart commits, > and since we can now do CR's on github, the only use FishEye has is > integration with jira. (close issues, bind commits to jira issues). > If there is another way of getting functionality like that, I think we > should go for it. > > Regards, > > > > On 14-10-2017 17:38, Colin Finck wrote: > >> Hi all! >> >> Our two Atlassian tools JIRA and FishEye have been unavailable for some >> hours again. I have brought JIRA back up, but FishEye has been eating >> RAM and CPU like crazy again. In my opinion, this is unacceptable for a >> tool that is just a simple commit browser to us. Also I don't have any >> time to constantly monitor it this weekend, so I'm leaving it shut down >> for now. >> >> With us having https://github.com/reactos/reactos/commits/master and >> https://git.reactos.org/?p=reactos.git;a=summary now, do we still need >> FishEye at all? >> If so, please tell me what features of it you would miss if it stays >> down. Maybe there are other alternatives. >> >> My last FishEye "performance" bug report took 3 months to resolve, and >> I'm reluctant to go the same route again for another such bug.. >> >> >> Cheers, >> >> Colin >> >> _______________________________________________ >> Ros-dev mailing list >> Ros-dev@reactos.org >> http://www.reactos.org/mailman/listinfo/ros-dev >> > > > _______________________________________________ > Ros-dev mailing list > Ros-dev@reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev >
_______________________________________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
