CMS

To allow Continuous Integration / Delivery / Deploy for CMSDisplay, the following tasks need are needed :

• Dockerize CMSDisplay
• Migrate Kafka Server from Confluence to lab.fernando.engineer and specialized topics for test and prod environments.
  - Depends on: Deploy dedicate Kafka Broker and include specialized topics in TrackHandler profiles .
• Specialize RabbitMQ queues for test and prod environments.
  - Depends on: include specialized RabbitMQ queues in TrackHandler profiles .
• Create a multi-topic branch CMSDisplay_Sonar Jenkins pipeline to trigger SonarQube code analysis .

Test Env:

• Create a muti-topic branch CMS_IntegrationTest Jenkins Pipeline w/ steps:

Production Env: (Release periodicity is intended to be weekly, but patches can be released at any time and will override current weekly release.)

• Create a release branch CMSDisplay_Deliver Jenkins pipeline
  - (This pipeline shall be used only over 'releases' branches and shall be compliant with other CMS artifacts in the same 'main' release.
• Modify current TrackHandler_Delivery Jenkins pipeline policy to be used only over 'release' branches.
• Modify the current TrackHandler_CodeQualityCheck Jenkins pipeline to allow 'per branch' analysis on SonarQube.
• Create CMS_Deploy Jenkins pipeline
• Modify nginx cms.lab.fernando.engineer.conf at lab.fernando.engineer according.

- Document the process Guidelines and Definition of Done.