As mentioned here:
The main aim of CI is to prevent integration problems, referred to as "integration hell"
Our project is a 3-tier web application, with frontend(Angular 6), backend(Springboot) & Database layer
For front end code(Angular 6), we have one source code repository(
For back end(SpringBoot), we have two source code repositories(
For database layer(Java & MySQL), we have three source code repositories(
Currently code has unit test cases.
As per the CI work flow mentioned in wiki,
When embarking on a change, a developer takes a copy of the current code base on which to work. As other developers submit changed code to the source code repository, this copy gradually ceases to reflect the repository code. Not only can the existing code base change, but new code can be added as well as new libraries, and other resources that create dependencies, and potential conflicts.
The longer a branch of code remains checked out, the greater the risk of multiple integration conflicts and failures when the developer branch is reintegrated into the main line. When developers submit code to the repository they must first update their code to reflect the changes in the repository since they took their copy. The more changes the repository contains, the more work developers must do before submitting their own changes.
Eventually, the repository may become so different from the developers' baselines that they enter what is sometimes referred to as "merge hell", or "integration hell", where the time it takes to integrate exceeds the time it took to make their original changes.
Continuous integration involves integrating early and often, so as to avoid the pitfalls of "integration hell". The practice aims to reduce rework and thus reduce cost and time.
1) To perform integration tests, s it recommended to have source code(angular_frontend/java_back_end/database) in a single repo(.git)?
2) Is it a good practice to maintain single source code repository for complete code(fullstack)? for running CI/CD pipeline...