[{"data":1,"prerenderedAt":117},["ShallowReactive",2],{"glossary-page-\u002Fglossary\u002Fteamcity":3},{"id":4,"title":5,"body":6,"description":104,"extension":105,"meta":106,"navigation":112,"path":113,"seo":114,"stem":115,"__hash__":116},"docs\u002Fglossary\u002Fteamcity.md","TeamCity",{"type":7,"value":8,"toc":96},"minimark",[9,15,20,26,30,33,59,63,72,76],[10,11,12],"glossary-title",{},[13,14,5],"p",{},[16,17,19],"h2",{"id":18},"what-is-teamcity","What Is TeamCity?",[13,21,22,25],{},[23,24,5],"strong",{}," is a CI\u002FCD server used to automate software builds, tests, and release workflows.\nIt is commonly used in teams that need flexible build orchestration and stronger control over internal delivery automation.",[16,27,29],{"id":28},"why-teamcity-matters","Why TeamCity Matters",[13,31,32],{},"TeamCity helps teams:",[34,35,36,43,48,53],"ul",{},[37,38,39,42],"li",{},[23,40,41],{},"automate build and test processes",",",[37,44,45,42],{},[23,46,47],{},"standardize delivery workflows",[37,49,50,42],{},[23,51,52],{},"reduce manual release overhead",[37,54,55,58],{},[23,56,57],{},"generate delivery events useful for engineering analysis",".\nIt becomes especially relevant when release behavior needs to be observable across many pipelines, services, and teams.",[16,60,62],{"id":61},"how-oobeya-uses-teamcity","How Oobeya Uses TeamCity",[13,64,65,66,71],{},"Oobeya can use TeamCity as a CI\u002FCD integration point for software delivery analysis, especially when organizations need deployment-related visibility beyond source control data. Teams comparing tool coverage can also see how it fits into Oobeya's ",[67,68,70],"a",{"href":69},"\u002Fintegrations","integration catalog",".\nThis helps teams include build and release behavior in engineering performance discussions instead of limiting visibility to repository activity alone.",[16,73,75],{"id":74},"related-terms","Related Terms",[34,77,78,84,90],{},[37,79,80],{},[67,81,83],{"href":82},"\u002Fglossary\u002Fcontinuous-integration","Continuous Integration",[37,85,86],{},[67,87,89],{"href":88},"\u002Fglossary\u002Fdeployment-pipeline","Deployment Pipeline",[37,91,92],{},[67,93,95],{"href":94},"\u002Fglossary\u002Flead-time-for-changes","Lead Time For Changes",{"title":97,"searchDepth":98,"depth":98,"links":99},"",2,[100,101,102,103],{"id":18,"depth":98,"text":19},{"id":28,"depth":98,"text":29},{"id":61,"depth":98,"text":62},{"id":74,"depth":98,"text":75},"TeamCity is a CI\u002FCD server used to automate builds, tests, and release workflows across pipelines where delivery visibility matters.","md",{"category":107,"tags":108},"T",[109,110,111],"CI\u002FCD","Automation","Software Delivery",true,"\u002Fglossary\u002Fteamcity",{"title":5,"description":104},"glossary\u002Fteamcity","LOqfW7KX_V3H_GnWoje5siFUF1RUuXDGemD5bnd2uCs",1775216702652]