Implement Environment Deployment Workflows

[emvaldes]

This is a stage where we will have to structure both the Front-End and Back-End as well loosely-coupled process.
Each release candidates exist on their own pipeline in a not inter-dependent relationship but at this specific stage they must be bundled into a unified workflow. At a later point, this final stage will need to be further refined.

This specific pipeline should not be executed on a scheduled basis because of the current level of effectiveness these have right now and lack of trust to them right now. Nevertheless, these pipelines must be available for ad-hoc requests.

What is the Definition of Done:

• For a while, this specific functional and automated pipeline should be operated as ad-hoc requests. It will contain a set of inter-dependent modules (release candidates) in other workflows.

Considerations: It's my professional opinion that having and maintaining a PRODUCTION branch as well as set of DEPLOYMENT branches is not correct. Using the RELEASE tags should be more than enough.

Note: These DEPLOYMENT branches are technically RELEASE branches and are eventually removed.