具有可用 Eclipse Mylyn 支持的 git 分布式问题跟踪器？
我使用 git 进行版本控制，但目前缺少一个与 Eclipse Mylyn 集成的良好问题/错误/票据跟踪器。
我正在寻找的功能：
- 开源实现（以便我可以添加将来需要的功能。GPL、LGPL、MIT 或 BSD 许可证优先）。
- 分布式（问题必须存储在 git 存储库中，我愿意为将问题存储在与代码相同或单独的分支中的跟踪器提供建议）。
- 必须有 Eclipse Mylyn 支持（以便我可以通过 mylyn 接口打开和关闭问题，我认为明智的实现可以在特定端口中提供本地主机 HTTP 服务器，并且 mylyn 将使用“Web 模板”连接器与问题跟踪器交谈）。最好是，当我切换分支时，Mylyn 会自动看到打开和关闭的问题，但我同意这不太聪明。
- 能够跟踪分支之间的问题，例如：
- 我有分支 X 和 Y 以及共同的父提交 Z。
- 提交 Z 有一个未解决的问题 Z1。
- 分支 Y 已修复（提交 Y4）并关闭 Y 中的问题。
- 分支 Y 有一个新问题（提交 Y2）
- 分支 Y 合并到 X 中。
- 问题跟踪器自动知道问题 Z1 已在 X 中修复，但现在提交 Y2 出现了新问题。
- 能够处理多个存储库打开、修改和关闭相同或不同问题的情况（分布式部分，我只是明确说明）。
- 必须可在 64 位和 32 位 Linux 上运行（目前为 ubuntu 10.04）
- 最好用 bash、c/c++、python 或 perl（也可能是 java 或 ruby）实现。
次要功能（会很好，但我可以没有）：
- 足够小，可以包含在项目的源代码中： 最好是具有可执行位集的单个文件（例如，具有完整实现的单个 bash 或 python 脚本）
- 某种 Web 用户界面，以便没有 Eclipse Mylyn 的人至少可以添加新问题并向现有问题添加评论（不需要能够设置优先级甚至关闭问题）
您可以提出任何建议吗？
更新：截至2012年9月13日尚未找到合适的工具。到目前为止最佳匹配的摘要：
- Bugs Everywhere - 没有 Mylyn 支持，状态一直是“Adrian Wilkins 希望看到过去两年“Plannet 功能”中的“BE 的 Mylyn 连接器”。否则该项目将继续进行。
- git-issues - 这个项目似乎已经死了。原作者大约两年前停止提交，而其他作者在过去两年大约完成了不到十次提交。
- git-case - 这个项目似乎已经死了。原作者三年前停止提交。
- stick - 这个项目似乎已经死了。我什至找不到公共存储库了。
- TicGit 这个项目似乎已经死了。我能找到的所有存储库都声明该项目不再开发。
- TigGit-NG - 这个项目似乎已经死亡多次，但到目前为止，总是有人再次采用该项目。这里也没有 Mylyn 支持。需要最新的 Ruby 环境才能运行。
- TicGit.net - 这个项目似乎是用 C# 编写的 TicGit 的 win32/.Net 特定分支。不符合我的需求。
I'm using git for version control but I'm currently lacking a good issue/bug/ticket tracker with Eclipse Mylyn integration.
The features I'm looking for:
- Open source implementation (so that I can add the features I need in the future. GPL, LGPL, MIT or BSD license preferred).
- Distributed (the issues must be stored in git the repository, I'm open for suggestions for trackers that store issues in the same or separate branch to the code).
- Must have Eclipse Mylyn support (so that I can open and close issues through mylyn interface, I think a sensible implementation could provide a localhost HTTP server in a specific port and mylyn would use "web template" connector to speak with the issue tracker). Preferably the Mylyn would automatically see issues opening and closing as I switch branches but I'm okay with this being less smart.
- Able to track issues between branches, example:
- I have branches X and Y with a common parent commit Z.
- the commit Z has an open issue Z1.
- the branch Y has a fix (commit Y4) and closes the issue in Y.
- the branch Y has a new issue (commit Y2)
- the branch Y is merged in X.
- the issue tracker automatically knows that the issue Z1 is fixed in X but there's now a new issue from commit Y2.
- Able to deal with the case where multiple repositories open, modify and close same or different issues (the distributed part, I'm just making this explicit).
- Must be runnable on 64 bit and 32 bit linux (ubuntu 10.04 for now)
- Preferably implemented in bash, c/c++, python or perl (possibly java or ruby, too).
Secondary features (would be nice but I can live without):
- Small enough to be included in the project's source code: preferrably a single file with an executable bit set (e.g. a single bash or python script with full implementation)
- Some kind of web user interface so that people without Eclipse Mylyn can at least add new issues and add comments to existing ones (no need to be able to set priorities or even close issues)
Can you suggest anything?
Update: As of 2012-09-13 no suitable tool has been found. Summary of the best matches this far:
- Bugs Everywhere - no Mylyn support, the status has been "Adrian Wilkins would like to see a Mylyn connector for BE" in the "Plannet features" for the last two years. Otherwise the project keeps going.
- git-issues - this project seems to be dead. Original author stopped making commits about two years ago and other authors have done less than ten commits in about last two years.
- git-case - this project seems to be dead. The original author stopped making commits three years ago.
- stick - this project seems to be dead. I couldn't even find public repository anymore.
- TicGit this project seems to be dead. All repositories I could find have disclaimer that the project is no longer developed.
- TigGit-NG - this projects seems to have died multiple times but this far, somebody has always adopted the project again. No Mylyn support here either. Requires pretty recent Ruby environment to run.
- TicGit.net - this project seems to be win32/.Net specific fork of TicGit written in C#. Does not match my needs.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
您可以查看 GitIssues ，它与 git 命令行集成得很好。但遗憾的是，它不支持 Mylyn。尽管如此，创建 Mylyn 连接器应该很容易，因为它可以导出到 XML。
您可以查看分布式错误跟踪系统的列表。
You could have a look at GitIssues which is well integrated with the git command line. But sadly, it doesn't support Mylyn. Nevertheless it should be easy to create a Mylyn connector since it can export to XML.
You can have a look at this list of distributed bug tracking systems.
您是否看过Bugs Everywhere？页面上显示 Mylyn 支持仍然是一项请求的功能，但我认为它几乎满足您所有的其他要求。 （需要明确的是，我自己实际上还没有尝试过这个方法，但对我来说这看起来是一个非常明智的方法。）
Have you looked at Bugs Everywhere? It says on the page that Mylyn support is still a requested feature, but I think it meets almost all of your other requirements. (Just to be clear, I haven't actually tried out this myself, but it looks like a very sensible approach to me.)