Fogbugz、svn 集成不起作用。 (svn 托管于 wush.net)

发布于 2024-07-11 09:48:09 字数 1163 浏览 8 评论 0原文

我刚刚将两个项目切换到fogbugz,到目前为止我非常喜欢它。 FB 有一些功能可以让 trac 脱颖而出。 但是,我无法让 FB 指向 FB 问题中的修订。

我已经在 tortoisesvn 中设置了 bugid,并且一切正常 - 我可以在 GUI 中单击 bugid,然后会弹出一个fogbugz 浏览器,并显示正确的问题。 然而,相反的情况则不起作用。

我正在使用 wush 作为我的 svn 托管。
我看过 http://fogcreek.com/FogBugz/docs/60/ topic/sourcecontrol/setup/Subversion.html

https://support.wush.net/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=33&nav=0

但尚未弄清楚如何正确执行此操作。 我将 websvn 来宾帐户设置为具有对存储库的读取权限。

trac 和 svn 之间的集成运行良好。 我能够(从 trac 票证)看到链接到 SVN 提交中的评论的修订版中更改的源代码。

有没有人成功地将 FB 与 websvn/SVN 的 wush 托管集成?

编辑:

我也很高兴能够在 FB 问题中添加链接、参考甚至文本。 然而,似乎 FB 问题甚至没有被提交所触及。

编辑: 响应一张海报:

bugid 在 svnUI 中正确显示 - 也就是说,我可以单击 tortoisesvn 历史记录中的链接,它会在fogbugz 中显示 url。

不起作用的是:

  • 自动更新/插入签入评论到
  • FB 中的 FB 问题,没有返回到存储库/更改/等的链接。

I just switched two projects over to fogbugz and so far I like it a lot. FB has a few features that just blow trac out of the water. However, I am having trouble getting FB to point back to the revisions from within the FB issues.

I have set up the bugid in tortoisesvn and that all works - I can click on a bugid in the GUI and a fogbugz browser pops up with the correct issue. The reverse does not work however.

I am using wush for my svn hosting.
I have looked at
http://fogcreek.com/FogBugz/docs/60/topics/sourcecontrol/setup/Subversion.html

and

https://support.wush.net/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=33&nav=0

but have not figured out how to do it correctly. I set the websvn guest account to have read access to the repo.

The integrateion between trac and svn worked fine. I was able (from trac ticket) to see the source that changed in a revision that was linked to a comment in a SVN commit.

Has anyone had success with FB integration with wush hosting of websvn/SVN?

EDIT:

I would also be happy to just be able to have a link or a reference or even text put in the FB issue. However, it doesn;t seem that the FB issue is even touched by a commit.

EDIT:
In response to one poster:

The bugid is shown correctly in the svnUI - that is, I can click on a link in the history of the tortoisesvn and it brings up the url in fogbugz.

What is not working is:

  • auto updating/insertion of checkin comment into a FB issue
  • in FB, no link back to the repo/changes/etc.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(3

笨死的猪 2024-07-18 09:48:09

“自动更新/插入签入评论到 FB 问题”

由于这不起作用,这意味着钩子提交脚本未触发或无法到达您的 FogBugz 服务器。

看看这个:
http://www.fogcreek.com/ FogBugz/blog/post/Debugging-Subversion-Source-Control-Integration.aspx

编辑:

谢谢 - 我正在编辑这个,因为我想添加一点,然后投票给这个答案。

我终于让它工作了。 我必须更改标准 URL,并且必须将提交后脚本发送给我的提供商。

这是最终为我提供所有信息的网址

这个也有帮助
http://www.fogcreek.com/FogBugz/docs/ 60/topics/advanced/SourceControlIntegration.html

"auto updating/insertion of checkin comment into a FB issue"

Since that isn't working, it means the hook commit script is not firing or cannot reach your FogBugz server.

See this:
http://www.fogcreek.com/FogBugz/blog/post/Debugging-Subversion-Source-Control-Integration.aspx

EDIT:

Thanks - I am editing this because I want to add one bit, then vote for this answer.

I finally got it working. There was a little tweak in the standard url I had to change and I had to send the post commit script to my provider.

Here is the url that finally got it all together for me

This one helps too
http://www.fogcreek.com/FogBugz/docs/60/topics/advanced/SourceControlIntegration.html

甜中书 2024-07-18 09:48:09

尽管我们的 SVN 是本地托管的,但我们成功地将 FogBugz 与 SVN 结合使用。 我不确定您的问题是哪一部分遇到问题,因此我将描述我们必须做些什么才能使其发挥作用。

在 FogBugz 中正确配置源代码控制 URL 花了一些时间,但我们从基础开始构建它,直到得到我们想要的。

在 hooks 文件夹中创建脚本也花了一些时间,我们必须自定义每个脚本并将其硬编码到正确的存储库,因为它似乎没有动态创建正确的 URL。 我们还必须检查构建服务器是否可以通过互联网访问 FogBugz URL,因为我们位于公司防火墙后面。 也许这就是问题所在? 我对 WUSH 不太了解,但它是否包括互联网访问以执行 HTTP 获取 FogBugz?

如果您在问题中添加更多细节,我会尽力提供帮助,但我承认我只设置过一次集成,所以我不是专家 - 也许 FogBugz 支持是您最好的选择。

干杯

We successfully have FogBugz working with SVN although our SVN is hosted locally. I'm not sure form your question which part your having problems with so I'll describe what we had to do to make it work.

It took a while to correctly configure the source control URL in FogBugz but starting from basics we built this up until we got what we wanted.

It also took some time to create the script in the hooks folder and we had to customize each one and hard-code it to the right repository as it didn't seem to create the correct URL dynamically. We also had to check that the build server had Internet access to the FogBugz URL as we are behind a corporate firewall. Perhaps this is the issue? I do not know much about WUSH but will it include Internet access to perform the HTTP get to FogBugz?

If you add further detail to your question I'll try to help but I'll admit I've only set up the integration once so I'm not an expert - perhaps FogBugz support is your best option.

Cheers

半窗疏影 2024-07-18 09:48:09

我终于让它工作了。 我必须更改标准 URL,并且必须将提交后脚本发送给我的提供商。

这是最终为我提供所有信息的网址

这个也有帮助
http://www.fogcreek.com/FogBugz/docs/ 60/topics/advanced/SourceControlIntegration.html

I finally got it working. There was a little tweak i n the standard url I had to change and I had to send the post commit script to my provider.

Here is the url that finally got it all together for me

This one helps too
http://www.fogcreek.com/FogBugz/docs/60/topics/advanced/SourceControlIntegration.html

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文