If you’re a developer, you may well be familiar with the scenario. You’re writing code and you want to test your changes against a copy of the production database. One that’s representative of the size and distribution characteristics and retains referential integrity so that, when your changes are released, they won’t result in a failed deployment that will take hours to resolve. But there’s a problem. The database copy you’re working with isn’t up to the job.

After a successful rollout for Flyway Teams and Flyway Enterprise, we are pleased to announce Git integration has been extended to Flyway Community users for Flyway Desktop. Today, Flyway Community users can enjoy seamless version control for their databases, integrated with popular Git systems like Azure DevOps Git, AWS CodeCommit, GitHub, GitLab, and Bitbucket – to name a few.

We’re excited to share Flyway Pipelines with you, a new service available in preview for all Flyway users of our Community, Teams and Enterprise editions to view the health and history of their database changes through a single pane of glass. Over recent years, one of the biggest challenges Flyway users have shared with us is how to gain easy visibility of all the database changes that teams are developing and deploying with Flyway.

Data, and the way enterprises use data in areas like development and testing, has not traditionally been a focus for business leaders but that’s now changing. Data is more varied and complicated than ever before, for example, with enterprises using two or more different database platforms – and 40% using four or more. It’s also spread wider and further, with enterprises hosting their databases in a combination of cloud and on-premises infrastructures.

DevOps is now the norm for virtually every IT team in every sector. By integrating and automating software development processes, it removes laborious, manual tasks and enables teams to deliver value to end users faster and more efficiently.