In the following article, we will focus on the automated deployment process.
>If you are interested in learning more, please allow us to invite you to the webinar Development vs. Configuration – Salesforce for CIOs or IT Managers on June 16, 2020 at 4:00 PM.
More information can be found here.
In the first part, we will focus on setting the correct branch strategy – i.e. which branches are appropriate to use and how to work with them.
To set up an automated process, it is necessary to chinese overseas africa database determine which environments we will deploy to within the project. Depending on the number of environments, set the branch strategy in the GIT repository appropriately.
An interesting example of a branch strategy is git-flow. It is a workflow approach that makes working with git easier. Using prepared commands (one command from git-flow performs one or more operations from standard GIT commands), it is possible to create new branches or perform more complicated merges.
I personally see a complication in git-flow in the impossibility of setting permissions over individual branches. For proper functioning and full use of the possibilities that the workflow offers, it is necessary that each member has the right to push to each branch (including master). For this reason, we have adopted only the terminology that defines the development status of the ticket according to the prefix of the given branch.
The logic is as follows:
A how to work with ecommerce? essential tips for starting your online business new branch is created from develop. The subsequent merge is back to the develop branch .
Release – preparing for deployment from test to production. A new branch is created from develop, followed by a merge into the master branch .
Hotfix – a new branch is created from the master branch. When finished, the changes are pushed to both the master and develop branches.
If it is an enterprise project, the client will probably thailand data require a deployment model containing multiple environments.
Mostly used are:
UAT – acceptance environment, before deployment to production.
PROD – production environment