This article explains basic release flow only. Depending on the feature implementation details, there might be additional steps required such as updating applications that are common to both TCMH and Seafarer Services (SS), db scripts, LoV changes, etc. For more complex deployments, it might be a good idea to have a work item created that details additional steps and/or include these steps in the SMGS ticket.
Instructions
One week before anticipated release, be sure to create an SMGS ticket for any on-premise applications that must be deployed. /wiki/spaces/MAR/pages/158138386.
By now you might have a release branch created, ideally under a release folder in your code repository. If not, create a release branch and tag the ‘develop' branch with the release number for tracking purposes.
Create the application builds by running the TCMH pipelines at this location against your release branch. They need to be executed individually because they are not set to trigger automatically. Please note that the Azure pipeline will containerize the CertificateProcessingRemote.API application and push to the shared container registry at this location.
…