TeamCity 用户：几个问题
这些问题仅适用于 TeamCity 用户
1) 是否可以配置 TeamCity 以根据您自己的正则表达式提取构建工件信息？ 这正是 Pulse 在此处所做的
2) TeamCity 是否与任何任务集成/错误跟踪工具？ 像吉拉一样？
3）这个问题仅适用于运行静态代码分析器的人。 像 PC-Lint/Visual Lint 这样的工具可以生成 XML 报告。 TeamCity 是否可以配置为解析这些工件并生成构建失败？
4) 我目前正在评估 TeamCity...社区论坛似乎不太活跃。 对于那些付费支持的人来说，Jetbrains 的支持如何？ 好吗？ Atlassian 似乎要好得多。
These questions are for TeamCity users only
1) Is it possible to configure TeamCity to extract build artifact information based on your own your regular expressions? This is exactly what Pulse does here
2) Does TeamCity integrate with any task/bug tracking tool? like JIRA?
3) This question is for people who run static code analyzer only. A tool like PC-Lint/Visual Lint can generate XML reports. Can TeamCity be configured to parse these artifacts and generate a build failure?
4) I'm currently evaluating TeamCity right now...there community forum doesnt seem to be very active. For those who pay for support, how is Jetbrains support? Is it good? Atlassian seems to be much better.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
TeamCity 允许使用基于 Ant 的模式获取构建工件。 您可以指定多个模式并为每个模式设置目标目录。 欲了解更多信息，请访问 http://www.jetbrains.net/confluence/display/TCD4/ Build+Artifact
有一个集成允许将 RF-3432 链接到 Jira 问题。 更高级的集成可能会出现在 TC 的下一个版本中。 欲了解更多信息，请访问 http://www.jetbrains.net/ confluence/display/TCD4/Mapping+External+Links+in+Comments
仅使用自定义插件。 或者您的构建过程可以发送特定的“回显”消息，这将更改构建状态和描述。
好的，我是 JetBrainer。 也许我们不会立即回复，但我们会努力尽快回答论坛问题。 付费客户还可以享受电子邮件支持。
希望这可以帮助，
基尔
TeamCity allows to get build artifacts with a Ant-based pattern. You can specify multiple patterns and set target directory for each pattern. Read more at http://www.jetbrains.net/confluence/display/TCD4/Build+Artifact
There is an integration which allows to link RF-3432 to the Jira issue. More advanced integration may appear in the next release of TC. Read more at http://www.jetbrains.net/confluence/display/TCD4/Mapping+External+Links+in+Comments
Only with custom plugin. Or your build process can send a specific "echo" message which will change build status and description.
OK, I'm JetBrainer. May be we don't response immediately, but we strive to answer forum questions ASAP. Paid customers also have e-mail support.
Hope this helps,
KIR
免责声明：我不为 JetBrains 工作！ 但我在目前的工作中曾使用过 Pulse 和 TeamCity。
构建工件：是的，TeamCity 将导出构建后保留的工件。 您可以添加定义 ant 样式通配符模式来匹配文件（默认模式匹配根构建目录中剩余的任何文件）。 这些文件可以从每个单独构建的项目视图中看到。
您可以使用特殊的服务命令 在构建脚本中也可以立即导出工件，我为生成 xml 文件的代码复杂性工具执行此操作，我还为其定义了自定义图表。
错误跟踪：我没有这方面的经验，但是KIR 指出了一些替代方案。
XML解析：你可以用ant来控制它。 我在我的构建中包含了一个名为 andariel 的第三方工具，它可以跨 xml 文档运行 XPath，然后使用服务消息导出要在自定义图表中显示的结果（在本例中是超过复杂性限制的方法计数）。
我相信您还可以发布工件，为 TeamCity 提供 XSL 来呈现 XML，并在构建结果中创建一个附加选项卡来显示它（但是我没有这样做）
技术支持：我我发现社区论坛非常好，我在一两天内就得到了平民和 Jetbrains 员工的回答，而且我使用的是免费的“专业”版本。
我只能想象电子邮件支持即使不是更好，也同样好！
Disclaimer: I don't work for JetBrains! But I've worked with Pulse and TeamCity in my current job.
Build Artifacts: Yes, TeamCity will export artifacts that remain after a build. You can add define ant-style wildcard patterns to match files (the default pattern matches any files left in the root build directory). These files can be seen from the project view against each individual build.
You can use special service commands in a build script to immediately export artifacts along the way too, I do this for a code complexity tool that generates xml files, for which I've also defined a custom graph.
Bug Tracking: I don't have experience with this, but KIR pointed out some alternatives.
XML Parsing: You can control this with ant. I included a third-party tool called andariel in my build that can run XPaths across xml documents, then used service messages to export the result (in this case a count of methods exceeding a complexity limit) to be displayed in a custom graph.
I believe you could also publish the artifacts, provide TeamCity with an XSL to render the XML, and create an additional tab in your build results to display it (however I have not done this)
Tech Support: I've found the community forums to be pretty good, most questions I've had answered within a day or two by both civilians and Jetbrains employees, and I was using the free 'Professional' version.
I can only imagine that email support will be just as good if not better!
我对这个问题有点困惑，因为我使用 TeamCity、TC（我猜 TC 的设计原则）是允许构建脚本（而不是 TC）保持构建命令的对应性。
换句话说，如果您需要 TeamCity 做一些很酷的事情，只需使用构建系统中的现有任务或自己编写一个任务将这些很酷的东西添加到您的构建脚本中即可。
TeamCity 支持 NAnt、MSBuild、Ant，并且确信您可以在构建代理上安装任何其他构建平台。
我希望 TC 或任何其他 CI 平台具有的唯一集成是与我选择的 SC 的源代码控制集成。 集成的其余部分应该由我的构建脚本控制。 这样，我只在每个项目的项目开始时配置一次 TC，然后就不再碰它了。 相反，每个版本的构建都可能会发生变化。
因此，理论上，通过构建脚本，您的问题的间接答案是肯定的。
希望这可以帮助。
I am a little confused about this question because my use of TeamCity, TC (and I guess the design principles of TC) is to allow the build script (and not TC) to remain the correspondent of build imperatives.
In other words, if you need TeamCity to do something cool, just add that cool stuff in your build script either using an existing task in your build system or write one yourself.
TeamCity supports NAnt, MSBuild, Ant and am sure, any other build platform you can install on on the buildagents.
The only integration I will want TC or any other CI platform to have is source control integration with my choice of SC. The rest of the integration should be controlled by my build script. That way, I only configure my TC once at the beginning of project for each project and then, don't touch it ever again. In contrast, the build can change per version.
So, the indirect answer to your question is Yes, theoretically, through the build script.
Hope this helps.