[{"data":1,"prerenderedAt":131},["ShallowReactive",2],{"glossary-page-\u002Fglossary\u002Fcontinuous-integration":3},{"id":4,"title":5,"body":6,"description":118,"extension":119,"meta":120,"navigation":126,"path":127,"seo":128,"stem":129,"__hash__":130},"docs\u002Fglossary\u002Fcontinuous-integration.md","Continuous Integration",{"type":7,"value":8,"toc":110},"minimark",[9,15,20,27,31,34,61,65,68,71,85,89],[10,11,12],"glossary-title",{},[13,14,5],"p",{},[16,17,19],"h2",{"id":18},"what-is-continuous-integration","What Is Continuous Integration?",[13,21,22,26],{},[23,24,25],"strong",{},"Continuous Integration (CI)"," is the practice of frequently merging changes into a shared branch and validating each change with automated builds, tests, and other checks.",[16,28,30],{"id":29},"why-continuous-integration-matters","Why Continuous Integration Matters",[13,32,33],{},"CI helps teams:",[35,36,37,44,50,55],"ul",{},[38,39,40,43],"li",{},[23,41,42],{},"catch integration issues early",",",[38,45,46,49],{},[23,47,48],{},"reduce merge risk"," by integrating smaller changes more often,",[38,51,52,43],{},[23,53,54],{},"improve release confidence",[38,56,57,60],{},[23,58,59],{},"create a reliable foundation for delivery automation",".",[16,62,64],{"id":63},"how-continuous-integration-is-applied","How Continuous Integration Is Applied",[13,66,67],{},"A strong CI system usually runs on every commit or pull request and verifies that code can build, test, and meet quality requirements before merge. The goal is fast feedback, not just more automation.",[13,69,70],{},"Good CI usually includes:",[35,72,73,76,79,82],{},[38,74,75],{},"automated test execution,",[38,77,78],{},"build verification,",[38,80,81],{},"consistent branch protection,",[38,83,84],{},"short feedback cycles for developers.",[16,86,88],{"id":87},"related-terms","Related Terms",[35,90,91,98,104],{},[38,92,93],{},[94,95,97],"a",{"href":96},"\u002Fglossary\u002Fcontinuous-delivery","Continuous Delivery",[38,99,100],{},[94,101,103],{"href":102},"\u002Fglossary\u002Fdeployment-pipeline","Deployment Pipeline",[38,105,106],{},[94,107,109],{"href":108},"\u002Fglossary\u002Flead-time-for-changes","Lead Time For Changes",{"title":111,"searchDepth":112,"depth":112,"links":113},"",2,[114,115,116,117],{"id":18,"depth":112,"text":19},{"id":29,"depth":112,"text":30},{"id":63,"depth":112,"text":64},{"id":87,"depth":112,"text":88},"Continuous Integration is the practice of frequently merging changes into a shared branch and validating them with automated checks.","md",{"category":121,"tags":122},"C",[123,124,125],"CI\u002FCD","DevOps","Software Delivery",true,"\u002Fglossary\u002Fcontinuous-integration",{"title":5,"description":118},"glossary\u002Fcontinuous-integration","ae1CudDmA4CjBUj3p8I-Ao6Ea0JzAeF_GI2ODwkqlzA",1775216701151]