CONTINOUS INTEGRATION:
1. Continuous Integration is a development practice that require developers to integrate code into a shared repository multiple times a day.
2. It is verified by an automated tests.
WHY CI:
1. Get Issue earliest (easy debug)
2. Transparency of what happening (everyone can see the build details)
3. Automated Build Creation
4. Manage/Validate artifacts
5. Will Support to continuous Deployment
6. Unify the system process
7. Helps to Deliver on time
8. Ownership for own code.
BENEFITS OF CI:
1. Develop and compile
2. Perform unit tests
3. Integrate with Database
4. Perform preproduction deployment
5. Perform functional tests and code labelling
6. Generate reports and analyze
CONTINUOUS DEPLOYMENT:
1. It is a future step from Continuous Delivery
2. It is a practice that aims at continuously releasing the code changes into the production environment.
3. Faster feedback from end users on each new feature as it is released to production.
WHY CD:
2. The goal Continuous Deployment is to run the codes and maintain a simulated environment.
1. Continuous Deployment takes into consideration the quality and the real-time monitoring of the product.
BENEFITS OF CD:
1. Continuous deployment is highly automated process
2. Scripts take over manual work during deployment
3. Scripts create the computing environment before deployment.
4. Automation increases accuracy.
– Content by Sandhya Anitha