Skip to content

Deployment Component

Introduction

This space contains document that create CICD pipelines with following detail information:

This space will contain strategies for release code for the Innotech group.

a) Trigger Plan: when push code, PR to production branch, etc,...

b) Logic Implement Model: the infrastructure, the components of process

c) Target Deployment: Remote Host, Serverless Fargate,...

d) Notification: Slack (for success deployment), Email (for failed deploy).

Git Strategy

We ship our code at a system, so we need to have a production process to deploy our code.

Using Github Actions

Github Strategy: Follow dev/ master/ production branches.

Verified Envirnoment Variable:

There are

Push on master > Satisfied Check [All good] > Deploy to production master

Currently

Release branch

Release Title

Release Note

Automatically release code

https://www.freecodecamp.org/news/a-beginners-guide-to-git-what-is-a-changelog-and-how-to-generate-it/

Deployment checklist

There will be full mark check with below tasks for a deployment.

  • Environment file is update with components

  • Strategy for roll up-down with compatitable version

  • Healthy state of remote host servers

  • Devlopement Testing phases status with done status

  • Deployment Physical Design & Tech decisions (Docs - if available)

For developer

For maintainer

  • release

gh release create v

Compliance

Follow Tips and best practices

Compliance

Source Reference

[3] Release Management on Github About releases - GitHub Docs

[4] Git Branch Strategy

[5] Git Branch Model

[6] Deploying ASGI application method with Flask Deploy Method