As we do not have CI setup for the project, so it can become difficult to trace the commits where the module crashes or at what point the build fails.
So, to eradicate this problem, a CI is needed to be setup to ease the CD as well.
Note: This issue is going to be handled by me
I'll be making use of gitlab-ci via pipelines and jobs for this.
Procedure(Sequential)
- Add current repo for external ci and cd on gitlab:-> references
- Make sure mirroring works fine on gitlab
- Open a PR here that contains ci script
All this is a part of devOps, for those who don't know what devOps is, i'm attaching few tickets to get an idea of CI and CD
As we do not have CI setup for the project, so it can become difficult to trace the commits where the module crashes or at what point the build fails.
So, to eradicate this problem, a CI is needed to be setup to ease the CD as well.
Note: This issue is going to be handled by me
I'll be making use of gitlab-ci via pipelines and jobs for this.
Procedure(Sequential)
All this is a part of devOps, for those who don't know what devOps is, i'm attaching few tickets to get an idea of CI and CD