With Git platforms like Bitbucket, GitLab, GitHub, Azure DevOps offered on the cloud, it is now easier than ever to create code repositories on a platform that you prefer. Devbridge can help to choose the right platform in an unbiased way.
Right platform, correct approach, effective processes
Distributed source control, and more specifically, Git, is de-facto storage for source code of your applications, infrastructure & test automation scripts, data processing flows, and BI reports. Choosing the right Git platform and methodology is a make-or-break moment for successful digital product delivery.
If it’s not in source control – it doesn’t exist
There is no “one size fits all” branching strategy
Continuously improve via pull request process
Just facts
With Git platforms offered on the cloud, it is now easier than ever to create code repositories on a platform that you prefer.
Most popular platforms like Bitbucket, GitLab, GitHub, Azure DevOps, offer free tier which is suitable to host open-source projects. Enterprise tiers are available for dedicated space for controlling employee and vendor access or advanced automation and reporting.
There are several popular branching strategies that you can adopt, the most popular are git-flow (a.k.a. long-lived feature branches) and trunk-based development.
If it’s not in source control, it doesn’t exist.
Apart from the obvious storing source code of your applications in source control, consider adopting Infrastructure as Code (IaC), Configuration as Code (CaC) practices to store them in Git as well. JMeter test scripts, database DDL scripts, reports, various scripting utilities written in python or bash, etc. should also be stored in Git.
There is no “one size fits all” branching strategy.
As described above, two main branching strategies are prominent. At Devbridge, we choose the right strategy based on client needs, product specifics, and timelines of the delivery.
Continuously improve via pull request process
Once a git platform is set up, corresponding repositories are created and branching strategy is determined for them, introduce pull request process. It will help disseminate knowledge within development team, identify risky code components, suggest improvements to labor-intensive development and deployment tasks.
Branching strategies: Git-flow vs. trunk-based development
Read article