How-To: Prod Release (Transferred to Wiki)

Schedule CAMMS Release - SM-GS Ticket

1. Go to http://smgs/sm/index.do & create a new ticket

2. Clone an existing ticket (e.g. C254845)

3. Modify the description section and add the goal of the sprint

4. Change the start date and end date of the Production Release.

5. In the Plan tab, change the name of the folder to the new ID

6. Close the ticket until it reaches the Change Assessment & Planning phase

7. Add an event in the CivAv Team Outlook calendar for the Prod Release

Note: For more details on how to create/clone a ticket, go to Creating a Change Request in SM-GS

IIS components (CAMMS-SMMAC-Ocelot, CAMIS-SIMAC-API)

1. Manually run the Prod pipeline(s) for the project

   • CAMMS-SMMAC-Publisher-prod

   • CAMIS-SIMAC-API-prod

   • CAMMS-SMMAC-Ocelot-prod

2. Copy the source code (\tctestmaster\tcappsroot\Saf-Sec-Sur\2\backup\) to the release folder created by Change Management related to the SM-GS ticket

3. If necessary, include an instruction file.

Cloud components (eMER-Listener, CAMMS Dashboard)

Once the IIS components have been deployed by the Web Team and we have confirmed and tested:

1. Manually run the build pipeline for the project: CAMMS-SMMAC-Dashboard-prod or EMER-Listener-prod

2. Open and approve the latest Release: CAMMS-SMMAC-Prod-Release or EMER-Listener-Prod-Release

3. For the eMER-Listener

   • Open Azure, restart the App services and click on the url link to be sure it will be restart.

Close SM-GS ticket