03 Jul Why I Favour Our Development Process
3. Feature Branch
If there is an issue on the live version of Frankli, a hotfix branch is made as a fork Master. Once the changes are reviewed, the branch is pulled into both Master and develop. Hotfixes are created with the naming scheme hotfix/FDS-001-Fix-Description. Prefixing branches in this way helps to make it clear what the purpose of a branch is.
Automated continuous deployment is key to our development process as it allows for consistency regarding deployments and saves a considerable amount of developer time. Whenever a push is made to master or develop, this kicks off a build in Bitbucket using “Bitbucket Pipelines”. Our automated test suite runs and, provided there are no failing tests, the branch is pushed live. This ensures we do not deploy a version with any (major) issues.
Having a powerful suite of tools in your development process that all work together with ease is crucial. Having such tools allows for consistency, clarity and accountability. This overall leads to the creation of a high-quality code base and subsequently results in high quality and reliable product.