当前位置： 文江博客话题详情

将 Fogbugz 与 TortoiseSVN 集成，无需 URL/Subversion 后端

发布于 2024-07-04 01:50:16 字数 209 浏览 15 评论 0原文

我已经安装了 TotroiseSVN，并且大部分存储库都从 C:\subversion\ 签入和签出，还有一些从网络共享签入和签出（当我最初发布这个问题时，我忘记了这一点）< /em>。

这意味着我本身没有“颠覆”服务器。

如何集成 TortoiseSVN 和 Fogbugz？

编辑：插入斜体

原文

I've got TotroiseSVN installed and have a majority of my repositories checking in and out from C:\subversion\ and a couple checking in and out from a network share (I forgot about this when I originally posted this question).

This means that I don't have a "subversion" server per-se.

How do I integrate TortoiseSVN and Fogbugz?

Edit: inserted italics

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

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

发布评论

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

评论（5）

停滞 2024-07-11 01:50:16

我一直在调查这个问题并设法让它发挥作用。 有一些小问题，但可以解决。

这个问题有 3 个不同的部分，如下所示：

  1. TortoiseSVN 部分 - 让 TortoiseSVN 在 svn 日志中插入 Bugid 和超链接

  2. FogBugz 部分 - 让 FogBugz 插入 SVN 信息和相应的链接

  3. WebSVN 部分 - 确保 FogBugz 的链接实际工作

第 1 部分的说明在另一个答案中，尽管它实际上比要求的要多。 关于钩子的内容实际上是第 2 部分的内容，正如所指出的 - 它不能“开箱即用”

只是为了确认，我们正在考虑使用 TortoiseSVN 不 SVN 服务器（即基于文件的存储库）

我使用 UNC 路径访问存储库，但它也适用于本地驱动器或映射驱动器。

所有这些都适用于TortoiseSVN v1.5.3和SVN Server v1.5.2（您需要安装SVN Server，因为第2部分需要svnlook.exe，它位于服务器包中。您实际上并不配置它作为 SVN 服务器）甚至可以从另一台计算机复制 svnlook.exe 并将其放在您的路径中的某个位置。

第 1 部分 - TortoiseSVN

为了获取 SVN 日志中的链接，只需要创建 TortoiseSVN 属性即可。

以前的说明工作正常，为了方便起见，我将在此处引用它们：

配置属性

  1. 右键单击您要使用的签出项目的根目录。

  2. 选择“TortoiseSVN -> 属性”

  3. 通过单击“新建...”并分别在“属性名称”和“属性值”中插入以下内容来添加五个属性值对：（确保为每个属性值对勾选“递归应用属性”）< /p>

    bugtraq:标签 BugzID: 
  bugtraq：消息 BugzID：%BUGID% 
  bugtraq：数字正确 
  bugtraq:url http://[这里是您的fogbugz URL]/default.asp?%BUGID% 
  bugtraq:warnifnoissue false

  4. 点击“确定”

正如 Jeff 所说，您需要为每个工作副本执行此操作，因此请按照他的说明迁移属性。

就是这样。 现在，当您提交时，TortoiseSVN 将添加指向相应 FogBugz bugID 的链接。 如果这就是你想要的，你可以停在这里。

第 2 部分 - FogBugz

为此，我们需要设置挂钩脚本。 基本上，批处理文件在每次提交后都会被调用，这又会调用 VBS 脚本来提交到 FogBugz。 VBS 脚本实际上在这种情况下工作得很好，因此我们不需要修改它。

问题是批处理文件被编写为作为服务器挂钩工作，但我们需要一个客户端挂钩。

SVN 服务器使用这些参数调用提交后挂钩：

<repository-path> <revision>

TortoiseSVN 使用这些参数调用提交后挂钩：

<affected-files> <depth> <messagefile> <revision> <error> <working-copy-path>

这就是它不起作用的原因 - 参数错误。 我们需要修改批处理文件，以便将正确的参数传递给 VBS 脚本。

您会注意到 TSVN 不传递存储库路径，这是一个问题，但它在以下情况下确实有效：

  • 存储库名称和工作副本名称相同
  • 您在工作副本的根目录下进行提交，不是子文件夹。

我将看看是否可以解决这个问题，如果可以，我会发回此处。

这是我修改后的批处理文件，它确实有效（请原谅过多的评论...）

您需要设置挂钩和存储库目录以匹配您的设置。

rem @echo off
rem   SubVersion -> FogBugz post-commit hook file
rem   Put this into the Hooks directory in your subversion repository
rem   along with the logBugDataSVN.vbs file

rem   TSVN calls this with args <PATH> <DEPTH> <MESSAGEFILE> <REVISION> <ERROR> <CWD>
rem   The ones we're interested in are <REVISION> and <CWD> which are %4 and %6

rem   YOU NEED TO EDIT THE LINE WHICH SETS RepoRoot TO POINT AT THE DIRECTORY 
rem   THAT CONTAINS YOUR REPOSITORIES AND ALSO YOU MUST SET THE HOOKS DIRECTORY

setlocal

rem   debugging
rem echo %1 %2 %3 %4 %5 %6 > c:\temp\test.txt

rem   Set Hooks directory location (no trailing slash)
set HooksDir=\\myserver\svn\hooks

rem   Set Repo Root location (ie. the directory containing all the repos)
rem   (no trailing slash)
set RepoRoot=\\myserver\svn

rem   Build full repo location
set Repo=%RepoRoot%\%~n6

rem   debugging
rem echo %Repo% >> c:\temp\test.txt

rem   Grab the last two digits of the revision number
rem   and append them to the log of svn changes
rem   to avoid simultaneous commit scenarios causing overwrites
set ChangeFileSuffix=%~4
set LogSvnChangeFile=svn%ChangeFileSuffix:~-2,2%.txt

set LogBugDataScript=logBugDataSVN.vbs
set ScriptCommand=cscript

rem   Could remove the need for svnlook on the client since TSVN 
rem   provides as parameters the info we need to call the script.
rem   However, it's in a slightly different format than the script is expecting
rem   for parsing, therefore we would have to amend the script too, so I won't bother.
rem @echo on
svnlook changed -r %4 %Repo% > %temp%\%LogSvnChangeFile%
svnlook log -r %4 %Repo% | %ScriptCommand% %HooksDir%\%LogBugDataScript% %4 %temp%\%LogSvnChangeFile% %~n6

del %temp%\%LogSvnChangeFile%
endlocal

我假设存储库位于 \\myserver\svn\ ，工作副本均位于 `C:\Projects\

  1. 进入您的 FogBugz 帐户并单击 Extras ->; 配置源代码管理集成

  2. 下载 Subversion 的 VBScript 文件（不必理会批处理文件）

  3. 创建一个文件夹以存储钩子脚本。 我将它放在与我的存储库相同的文件夹中。 例如。 \\myserver\svn\hooks\

  4. 重命名 VBscript 以删除文件名末尾的 .safe。

  5. 将我的批处理文件版本保存在您的 hooks 目录中，作为 post-commit-tsvn.bat

  6. 右键单击任意目录。

  7. 选择“TortoiseSVN > 设置”（在上一步的右键菜单中）

  8. 选择“Hook Scripts” ”

  9. 单击“添加”并设置属性如下：

    • 挂钩类型：提交后挂钩

    • 工作副本路径：C:\Projects（或所有项目的根目录所在的位置。）

    • 要执行的命令行：\\myserver\svn\hooks\post-commit-tsvn.bat（这需要指向您在步骤 3 中放置 hooks 目录的位置）< /p>

    • 勾选“等待脚本完成”

  10. 单击“确定”两次。

下次您提交并输入 Bugid 时，它将提交给 FogBugz。 这些链接不起作用，但至少有修订信息，您可以在 TortoiseSVN 中手动查找日志。

注意：您会注意到存储库根被硬编码到批处理文件中。 因此，如果您从不具有相同根目录的存储库中签出（例如，一个在本地驱动器上，一个在网络上），那么您将需要使用 2 个批处理文件和 TSVN 中的 Hook 脚本下的 2 个相应条目设置。 实现这一点的方法是拥有 2 个独立的工作副本树 - 每个存储库根目录都有一个工作副本树。

第 3 部分 - WebSVN

呃，我还没有这样做:-)

从阅读 WebSVN 文档来看，WebSVN 似乎并没有真正与 SVN 服务器集成，它只是像任何其他 SVN 客户端一样运行，但提供了一个 Web 界面。 理论上来说，它应该可以与基于文件的存储库一起正常工作。 不过我还没试过。

I've been investigating this issue and have managed to get it working. There are a couple of minor problems but they can be worked-around.

There are 3 distinct parts to this problem, as follows:

  1. The TortoiseSVN part - getting TortoiseSVN to insert the Bugid and hyperlink in the svn log

  2. The FogBugz part - getting FogBugz to insert the SVN info and corresponding links

  3. The WebSVN part - ensuring the links from FogBugz actually work

Instructions for part 1 are in another answer, although it actually does more than required. The stuff about the hooks is actually for part 2, and as is pointed out - it doesn't work "out of the box"

Just to confirm, we are looking at using TortoiseSVN WITHOUT an SVN server (ie. file-based repositories)

I'm accessing the repositories using UNC paths, but it also works for local drives or mapped drives.

All of this works with TortoiseSVN v1.5.3 and SVN Server v1.5.2 (You need to install SVN Server because part 2 needs svnlook.exe which is in the server package. You don't actually configure it to work as an SVN Server) It may even be possible to just copy svnlook.exe from another computer and put it somewhere in your path.

Part 1 - TortoiseSVN

Creating the TortoiseSVN properties is all that is required in order to get the links in the SVN log.

Previous instructions work fine, I'll quote them here for convenience:

Configure the Properties

  1. Right click on the root directory of the checked out project you want to work with.

  2. Select "TortoiseSVN -> Properties"

  3. Add five property value pairs by clicking "New..." and inserting the following in "Property Name" and "Property Value" respectively: (make sure you tick "Apply property recursively" for each one)

    bugtraq:label    BugzID:
bugtraq:message  BugzID: %BUGID%
bugtraq:number   true
bugtraq:url      http://[your fogbugz URL here]/default.asp?%BUGID%
bugtraq:warnifnoissue   false

  4. Click "OK"

As Jeff says, you'll need to do that for each working copy, so follow his instructions for migrating the properties.

That's it. TortoiseSVN will now add a link to the corresponding FogBugz bugID when you commit. If that's all you want, you can stop here.

Part 2 - FogBugz

For this to work we need to set up the hook scripts. Basically the batch file is called after each commit, and this in turn calls the VBS script which does the submission to FogBugz. The VBS script actually works fine in this situation so we don't need to modify it.

The problem is that the batch file is written to work as a server hook, but we need a client hook.

SVN server calls the post-commit hook with these parameters:

<repository-path> <revision>

TortoiseSVN calls the post-commit hook with these parameters:

<affected-files> <depth> <messagefile> <revision> <error> <working-copy-path>

So that's why it doesn't work - the parameters are wrong. We need to amend the batch file so it passes the correct parameters to the VBS script.

You'll notice that TSVN doesn't pass the repository path, which is a problem, but it does work in the following circumstances:

  • The repository name and working copy name are the same
  • You do the commit at the root of the working copy, not a subfolder.

I'm going to see if I can fix this problem and will post back here if I do.

Here's my amended batch file which does work (please excuse the excessive comments...)

You'll need to set the hook and repository directories to match your setup.

rem @echo off
rem   SubVersion -> FogBugz post-commit hook file
rem   Put this into the Hooks directory in your subversion repository
rem   along with the logBugDataSVN.vbs file

rem   TSVN calls this with args <PATH> <DEPTH> <MESSAGEFILE> <REVISION> <ERROR> <CWD>
rem   The ones we're interested in are <REVISION> and <CWD> which are %4 and %6

rem   YOU NEED TO EDIT THE LINE WHICH SETS RepoRoot TO POINT AT THE DIRECTORY 
rem   THAT CONTAINS YOUR REPOSITORIES AND ALSO YOU MUST SET THE HOOKS DIRECTORY

setlocal

rem   debugging
rem echo %1 %2 %3 %4 %5 %6 > c:\temp\test.txt

rem   Set Hooks directory location (no trailing slash)
set HooksDir=\\myserver\svn\hooks

rem   Set Repo Root location (ie. the directory containing all the repos)
rem   (no trailing slash)
set RepoRoot=\\myserver\svn

rem   Build full repo location
set Repo=%RepoRoot%\%~n6

rem   debugging
rem echo %Repo% >> c:\temp\test.txt

rem   Grab the last two digits of the revision number
rem   and append them to the log of svn changes
rem   to avoid simultaneous commit scenarios causing overwrites
set ChangeFileSuffix=%~4
set LogSvnChangeFile=svn%ChangeFileSuffix:~-2,2%.txt

set LogBugDataScript=logBugDataSVN.vbs
set ScriptCommand=cscript

rem   Could remove the need for svnlook on the client since TSVN 
rem   provides as parameters the info we need to call the script.
rem   However, it's in a slightly different format than the script is expecting
rem   for parsing, therefore we would have to amend the script too, so I won't bother.
rem @echo on
svnlook changed -r %4 %Repo% > %temp%\%LogSvnChangeFile%
svnlook log -r %4 %Repo% | %ScriptCommand% %HooksDir%\%LogBugDataScript% %4 %temp%\%LogSvnChangeFile% %~n6

del %temp%\%LogSvnChangeFile%
endlocal

I'm going to assume the repositories are at \\myserver\svn\ and working copies are all under `C:\Projects\

  1. Go into your FogBugz account and click Extras -> Configure Source Control Integration

  2. Download the VBScript file for Subversion (don't bother with the batch file)

  3. Create a folder to store the hook scripts. I put it in the same folder as my repositories. eg. \\myserver\svn\hooks\

  4. Rename VBscript to remove the .safe at the end of the filename.

  5. Save my version of the batch file in your hooks directory, as post-commit-tsvn.bat

  6. Right click on any directory.

  7. Select "TortoiseSVN > Settings" (in the right click menu from the last step)

  8. Select "Hook Scripts"

  9. Click "Add" and set the properties as follows:

    • Hook Type: Post-Commit Hook

    • Working Copy Path: C:\Projects (or whatever your root directory for all of your projects is.)

    • Command Line To Execute: \\myserver\svn\hooks\post-commit-tsvn.bat (this needs to point to wherever you put your hooks directory in step 3)

    • Tick "Wait for the script to finish"

  10. Click OK twice.

Next time you commit and enter a Bugid, it will be submitted to FogBugz. The links won't work but at least the revision info is there and you can manually look up the log in TortoiseSVN.

NOTE: You'll notice that the repository root is hard-coded into the batch file. As a result, if you check out from repositories that don't have the same root (eg. one on local drive and one on network) then you'll need to use 2 batch files and 2 corresponding entries under Hook Scripts in the TSVN settings. The way to do this would be to have 2 separate Working Copy trees - one for each repository root.

Part 3 - WebSVN

Errr, I haven't done this :-)

From reading the WebSVN docs, it seems that WebSVN doesn't actually integrate with the SVN server, it just behaves like any other SVN client but presents a web interface. In theory then it should work fine with a file-based repository. I haven't tried it though.

回复 原文
橘味果▽酱 2024-07-11 01:50:16

这个答案不完整且有缺陷！ 它仅适用于从 TortoisSVN 到 Fogbugz，反之则不行。 我仍然需要知道如何让它从 Fogbugz 向后工作（就像它的设计那样），以便我在查看错误时可以从 Fogbugz 中看到错误解决的修订号。

有用的 URL

http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-propertypage .html

http://tortoisesvn.net/issuetracker_integration

设置“挂钩”

  1. Go进入您的fogbugz 帐户并单击“附加”> 配置源代码管理集成

  2. 下载“post-commit.bat”和 Subversion 的 VBScript 文件

  3. 在常见的易于访问的位置（最好在文件路径中没有空格）

  4. 将文件的副本放在hooks 目录

  5. 重命名不带“.safe”扩展名的文件

  6. 右键单击任何目录。

  7. 选择“TortoiseSVN > 设置”（在上一步的右键菜单中）

  8. 选择“Hook Scripts” "

  1. 单击“添加”

  2. 设置属性：

    • 挂钩类型：提交后挂钩

    • 工作副本路径：C:\\Projects（或所有项目的根目录。如果您有多个项目，则需要为每个项目执行此步骤。）

    • 要执行的命令行：C:\\subversion\\hooks\\post-commit.bat（这需要指向您在步骤 3 中放置 hooks 目录的位置）

    • 我还选中了等待脚本完成的复选框...

警告：不要忘记双反斜杠！ “\\”

单击“确定”...

添加 Hook 脚本

注意：屏幕截图不同，按照文件路径的文本，而不是屏幕截图...

此时，您似乎可以单击“Issue Tracker Integration”并选择 Fogbugz。 没有。 它只是返回“没有可用的问题跟踪器提供商”。

  1. 点击“确定”关闭整个
    设置对话框窗口

配置属性

  1. 再次右键单击签出的根目录
    您想要使用的项目（您需要为每个项目执行此“配置属性”步骤 - 请参阅下面的“在项目之间迁移属性”）

  2. 选择“TortoiseSVN > 属性”（在右键单击菜单中）
    从上一步开始）

  3. 通过单击“新建...”并插入添加五个属性值对
    “属性名称”中的以下内容和
    “属性值”分别：

bugtraq:标签 BugzID:
bugtraq：消息 BugzID：%%BUGID%%

bugtraq：数字为真

bugtraq:url http://[您的fogbugz URL
这里]/default.asp?%BUGID%

bugtraq：warnifnoissue false

属性窗口
adding new property

  1. 单击“确定”

提交更改并查看日志

现在，当您提交时，您可以指定一个 bug提交地址。 这会迫使您在修复每个错误后提交...

specifying bug同学在提交时解决

当您查看日志时（右）点击项目根目录，TortoiseSVN > show log）你可以看到每次检查对应的bug id（1），如果你正在查看的话，你可以点击bug id号被带到fogbugz来自动查看该bug实际的日志消息。 相当漂亮！

在项目之间迁移属性

  1. 右键单击已具有正确属性配置的项目

  2. 选择“TortoiseSVN > Properties”（从步骤 1 的右键单击菜单中）

  3. 突出显示所有所需属性

  4. 单击“导出”

  5. 以属性命名文件，并将其放入一个易于访问的目录（我将我的目录与 hooks 文件一起放置）

保存属性对话框

  1. 右键单击需要设置属性的签出项目的根目录。

  2. 单击“导入”

  3. 选择您在上述步骤 4 中导出的文件

  4. 单击“打开”

This answer is incomplete and flawed! It only works from TortoisSVN to Fogbugz, but not the other way around. I still need to know how to get it to work backwards from Fogbugz (like it's designed to) so that I can see the Revision number a bug is addressed in from Fogbugz while looking at a bug.

Helpful URLS

http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-propertypage.html

http://tortoisesvn.net/issuetracker_integration

Set the "Hooks"

  1. Go into your fogbugz account and click Extras > Configure Source Control Integration

  2. Download "post-commit.bat" and the VBScript file for Subversion

  3. Create a "hooks" directory in a common easily accessed location (preferably with no spaces in the file path)

  4. Place a copy of the files in the hooks directories

  5. Rename the files without the ".safe" extension

  6. Right click on any directory.

  7. Select "TortoiseSVN > Settings" (in the right click menu from the last step)

  8. Select "Hook Scripts"

  1. Click "Add"

  2. Set the properties thus:

    • Hook Type: Post-Commit Hook

    • Working Copy Path: C:\\Projects (or whatever your root directory for all of your projects is. If you have multiple you will need to do this step for each one.)

    • Command Line To Execute: C:\\subversion\\hooks\\post-commit.bat (this needs to point to wherever you put your hooks directory from step 3)

    • I also selected the checkbox to Wait for the script to finish...

WARNING: Don't forget the double back-slash! "\\"

Click OK...

Adding a Hook Script

Note: the screenshot is different, follow the text for the file paths, NOT the screenshot...

At this point it would seem you could click "Issue Tracker Integration" and select Fogbugz. nope. It just returns "There are no issue-tracker providers available".

  1. Click "OK" to close the whole
    settings dialogue window

Configure the Properties

  1. Once again, Right click on the root directory of the checked out
    project you want to work with (you need to do this "configure the properties" step for each project -- See "Migrating Properties Between Projects" below)

  2. Select "TortoiseSVN > Properties" (in the right click menu
    from the last step)

  3. Add five property value pairs by clicking "New..." and inserting the
    following in "Property Name" and
    "Property Value" respectively:

bugtraq:label BugzID:
bugtraq:message BugzID: %%BUGID%%

bugtraq:number true

bugtraq:url http://[your fogbugz URL
here]/default.asp?%BUGID%

bugtraq:warnifnoissue false

properties window
adding new property

  1. Click "OK"

Commiting Changes and Viewing the Logs

Now when you are commiting, you can specify one bug that the commit addresses. This kind of forces you to commit after fixing each bug...

specifying bug addressed when commiting

When you view the log (Right click root of project, TortoiseSVN > show log) you can see the bug id that each checking corresponds to (1), and you can click the bug id number to be taken to fogbugz to view that bug automatically if you are looking at the actual log message. Pretty nifty!

Migrating Properties Between Projects

  1. Right click on a project that already has the proper Properties configuration

  2. Select "TortoiseSVN > Properties" (from the right-click menu from step 1)

  3. Highlight all of the desired properties

  4. Click "Export"

  5. Name the file after the property, and place in an easily accessible directory (I placed mine with the hooks files)

save properties dialogue

  1. Right click on the root directory of the checked out project needing properties set for.

  2. Click "Import"

  3. Select the file you exported in step 4 above

  4. Click Open

回复 原文
浅浅淡淡 2024-07-11 01:50:16

为什么不能简单地安装一个颠覆服务器？ 如果您下载免费的 VisualSVN Server，您将获得一个用于源代码的 http 服务器，并且可以因此，使用 FogBugz 脚本来集成两者。

我问的原因是因为到目前为止所有脚本和文档都假设您拥有服务器，客户端脚本对于 FogBugz 来说太新了，无法为其提供模板，因此您几乎只能依靠自己的设备来完成。

Why can't you simply install a subversion server? If you download VisualSVN Server, which is free, you get a http server for your source code and can thus use the FogBugz scripts for integrating the two.

The reason I'm asking is because all scripts and documentation so far assumes you have the server, client-side scripts are too new for FogBugz to have templates for them so you're pretty much left to your own devices on that.

回复 原文
尬尬 2024-07-11 01:50:16

问题是 FogBugz 将链接到网页，而 file:///etc 不是网页。 要以两种方式进行集成，您的 Subversion 存储库需要一个 Web 服务器。 设置 Apache 或其他可以以正确方式托管这些内容的东西。

The problem is that FogBugz will link to a web page, and file:///etc is not a web page. To get integration two ways, you need a web server for your subversion repository. Either set up Apache or something else that can host those things the proper way.

回复 原文
若无相欠,怎会相见 2024-07-11 01:50:16

我不确定我是否跟随你。 您的网络或 C:\ 驱动器上是否有存储库？ 根据您的两篇文章，您两者都有，或者都没有，或者其中之一，或者...

您无法让 VisualSVN 或 Apache 从网络共享安全地为存储库提供服务。 由于您最初说您的 C:\ 驱动器上有存储库，因此您会得到建议。 如果您有不同的设置，则需要告诉我们。

如果您的本地硬盘上有存储库，我会安装 VisualSVN，或将其集成到 Apache 中。 VisualSVN 可以与 Apache 一起正常运行，因此如果您选择这种方式，则只需安装它即可。 您也可以将现有存储库复制到 VisualSVN 的存储库根目录中，然后即可启动并运行。

我不确定为什么这里的这篇大文章被标记为不完整，因为它详细介绍了设置挂钩脚本以通知 FogBugz 有关与案例相关的新修订的必要步骤，这应该是不完整消息说不行。 那不行吗？

I am not sure I follow you. Do you have the repositories on the network or on your C:\ drive? According to two of your posts, you have both, or neither, or one of them or...

You can not get VisualSVN or Apache to safely serve repositories from a network share. Since you originally said you had the repositories on your C:\ drive, that's what you get advice for. If you have a different setup, you need to tell us about that.

If you have the repositories on your local harddisk, I would install VisualSVN, or integrate it into Apache. VisualSVN can run fine alongside Apache so if you go that route you only have to install it. Your existing repositories can also just be copied into the repository root directory of VisualSVN and you're up and running.

I am unsure why that big post here is labelled as incomplete, as it details the steps necessary to set up a hook script to inform FogBugz about the new revisions linked to the cases, which should be what the incomplete message says it doesn't do. Is that not working?

回复 原文
~没有更多了~

关于作者

奶茶白久

暂无简介

文章
评论
24 人气
发私信

相关话题

更多

热门标签

操作系统 程序设计 IT运维 Linux系统管理 JavaScript 服务器应用 solaris C/C++ PHP Shell BSD Vue.js aix Oracle Python HTML 系统管理 HTML5 CSS 前端
更多

推荐作者

Promise

文章 0 评论 0

qq_lbRlsh

文章 0 评论 0

待＂谢繁草

文章 0 评论 0

yy2010hell

文章 0 评论 0

漫无边际

文章 0 评论 0

傲娇萝莉攻

文章 0 评论 0

更多

友情链接

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