Continuous Integration: Developers commit code into a single repository frequently. At least daily, but more typically (n) times a day. Every commit triggers a pipeline that builds and tests the entire, integrated, code base.
This allows teams to catch regressions and breaking changes nearly as soon as they're introduced. The more frequently you commit, the more effective CI is.
Continuous Deployment/Delivery: To some degree, extends CI. CD refers to continuously deploying a commit as soon as it has been verified by the build and test stages.
Typically you'd break this into stages. First deploying to a "production-like" QA environment, then finally on to Production if no issues were present in QA.
Continuous Integration: Developers commit code into a single repository frequently. At least daily, but more typically (n) times a day. Every commit triggers a pipeline that builds and tests the entire, integrated, code base.
This allows teams to catch regressions and breaking changes nearly as soon as they're introduced. The more frequently you commit, the more effective CI is.
Continuous Deployment/Delivery: To some degree, extends CI. CD refers to continuously deploying a commit as soon as it has been verified by the build and test stages.
Typically you'd break this into stages. First deploying to a "production-like" QA environment, then finally on to Production if no issues were present in QA.
This is a very oversimplified overview. If any of the terms I used don't make sense, ThoughtWorks* has a slightly deeper overview here. Or Martin Fowlers article is much more in depth.
*full disclosure: This is not an ad. But I am a TWer :)
Thanks.