ACSF MBN Workflow

As illustrated in the following graph, this is general workflow idea:

1. develop branch is created from production
2. Ticket 1 branch is created from production.
3. Ticket 1 branch is merged into develop from a PR.
4. Jenkins creates a tag from develop branch and deploys it to DEV environment.
5. QA team can test on DEV
6. Ticket 2 branch is created from production.
7. Ticket 2 branch is merged into develop from a PR.
8. Jenkins creates a tag from develop branch and deploys it to DEV environment.
9. QA team can test on DEV
10. Release branch is created from production.
11. Some manually selected tickets branches are merged into release branch.
12. Release tag is created from release branch.
13. Release tag is deployed to TEST environment.
14. QA team test on TEST.
15. Release tag is deployed to LIVE environment.
16. QA team test on LIVE.

NOTE: Releases are the branches that get deployed further into staging/test environments. Not all releases are pushed to production.