Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p><em>Disclaimer:</em> I don't work for JetBrains! But I've worked with Pulse and TeamCity in my current job.</p> <p><strong>Build Artifacts</strong>: 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.</p> <p>You can use special <a href="http://www.jetbrains.net/confluence/display/TCD4/Build+Script+Interaction+with+TeamCity#BuildScriptInteractionwithTeamCity-artPublishing" rel="nofollow noreferrer">service commands</a> 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.</p> <p><strong>Bug Tracking</strong>: I don't have experience with this, but <a href="https://stackoverflow.com/questions/762692/teamcity-users-a-few-questions/901183#901183">KIR</a> pointed out some alternatives.</p> <p><strong>XML Parsing</strong>: You can control this with ant. I included a third-party tool called <a href="http://andariel.uworks.net" rel="nofollow noreferrer">andariel</a> 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.</p> <p>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)</p> <p><strong>Tech Support</strong>: 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!</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload