As a process, we set up a continuous-testing workflow where the master branch never breaks. We always encourage our customers to adapt a modular architecture but as a software development strategy we always prefer ‘Monorepo’ wherein the codes for various projects get stored in the same repository instead of using the complex. Multi-repo, wherein it uses various repositories to host the multiple codes of one project and the libraries have to be resynced constantly.
While we keep the codes stored, we can consider the Health Panel for the below usage:
- To keep track of the critical information about the current state of the project.
- As a gamification mechanism that encourages the developers to adhere to the industrial best practices.
- To keep the codes clean.
- Optionally, it can have links on Gitpod to test recent changes online.
In the process of setting up CI/CD, bundling, deployment and publishing occur during the later stages of such a pipeline. As per the type of your application,CI/CD either generates an installer or pushes it on to a server or registers it on a market. Additionally, we recommend setting up a self-hosted runner. We have extensively spent hours and hours on each aspect of this pipeline to create a tailored solution that is completely customizable as per your needs.