Roadmap to implement CICD components

The following tasks are identified to implement CICD components. This ticket can be converted to a milestone for better issue tracking.

• CICD Components
  • Refactor the .gitlab-ci.yml
  • Remove the variable suffixes specifying the app names in the CI job script to make them generic.
    • Change the variable names in the pipelines to these generic variable names. At this point ,all the CI job scripts for the builds would look the same. The only difference would be in the job name
  • Create a component project with a component each for a build, deploy, build_cleanup, and deploy_cleanup with suggested directory structure
    • Write a clear ReadMe.md with clear description.
  • Make a template for the build job with appropriate use of inputs wherever possible
  • Make a template for the deploy job with appropriate use of inputs wherever possible
  • Make a template for the build job cleanup with appropriate use of inputs wherever possible
  • Make a template for the deploy job cleanup with appropriate use of inputs wherever possible
  • Configure the Component project’s .gitlab-ci.yml to test the components

     Notes:
     - CICD for testing components. 
     - This will help us to test the infrastructure code and the CI separately from the application code.  
     Separation of Concerns.  
     This will avoid long wait times for the application code to compile and deploy when we want to test the infra code/CICD  
     We have three categories of apps:   
     1. Software build/deploy eg. OOD  
     2. Infra build/deploy eg. packer & TF  
     3. CI

    • Create a release job for the component on a tag push
      • You can still use a component without pushing it to the catalog