Continuous Integration (CI) is the process of automating the build and test of code every time a team member commits changes to the shared repository. When we say integrate, we’re pertaining to combining source codes, where developers can continuously introduce code changes in parallel.
CI promotes:
Early detection of bugs
Consistency for testing
Time-efficiency (also for QA team as they’ll spend less time testing!)
The goal of having fewer bugs in production
Faster feedback for pull-requests if set
So imagine you’re pushing new code changes in GitHub repository, and for each push, you get automatic feedback if the codes are safe or not by running unit tests in the background. Sounds cool, right? What if we say also that we can do it in pull-request– that for each creation, tests are run automatically and can visibly show the test result in pull-request details? Wow, amazing!
Introduction to CI
Continuous Integration (CI) is the process of automating the build and test of code every time a team member commits changes to the shared repository. When we say integrate, we’re pertaining to combining source codes, where developers can continuously introduce code changes in parallel.
CI promotes:
So imagine you’re pushing new code changes in GitHub repository, and for each push, you get automatic feedback if the codes are safe or not by running unit tests in the background. Sounds cool, right? What if we say also that we can do it in pull-request – that for each creation, tests are run automatically and can visibly show the test result in pull-request details? Wow, amazing!
<img style="width: 80%" src="https://cdn.hackerhero.com/1.1/a...