# Which database DevOps software solutions integrate with Jenkins, GitLab and GitHub for automated database release pipelines?

<p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">I’m putting together a roundup on CI/CD integration and trying to identify which database DevOps software works reliably with Jenkins, GitLab, and GitHub. “Integration” can mean anything from a native connector to a command wrapped in a script, so real-world experience matters.</p><ul>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/liquibase/reviews"><strong>Liquibase</strong></a><strong>:</strong> Its command-line design fits Jenkins and other pipelines, though initial setup takes work.</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/redgate-flyway/reviews"><strong>Redgate Flyway</strong></a><strong>:</strong> Supports validation through Jenkins, GitHub Actions, and GitLab CI.</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/harness-platform/reviews"><strong>Harness Platform</strong></a><strong>:</strong> Provides built-in connectors and broader automation, making it closer to a Jenkins replacement.</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/dbmaestro-dbmaestro-devops-platform/reviews"><strong>DBmaestro</strong></a><strong>:</strong> Adds database governance and compliance controls.</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/sql-toolbelt-essentials/reviews"><strong>SQL Toolbelt Essentials</strong></a><strong>:</strong> Supports SQL Server releases but is less suited to mixed-database projects.</li>
</ul><p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">Have you standardized database releases across all three platforms, or do you maintain separate configurations?</p>

##### Post Metadata
- Posted at: about 2 months ago
- Author title: Marketer
- Net upvotes: 1


## Comments
### Comment 1

&lt;p&gt;&lt;span style=&quot;color: rgb(0, 0, 0);&quot;&gt;The reason that approach holds is that a command-line first tool makes each CI platform a thin wrapper, so the migration logic lives in the repository rather than in three different pipeline configurations. Anything expressed as a native connector has to be re-expressed per platform, and those versions drift. Liquibase&#39;s command-line design being called out is exactly that property. Worth checking the tool also runs identically on a developer laptop, since a migration you cannot reproduce locally is one you will only ever debug in CI.&lt;/span&gt;&lt;/p&gt;

##### Comment Metadata
- Posted at: 5 days ago
- Author title: Tech Consultant



### Comment 2

We eventually standardized on a shared release process across Jenkins, GitLab, and GitHub. Redgate Flyway and Liquibase made that much easier because the migration workflow stayed consistent, while platform-specific steps were kept to a minimum.

##### Comment Metadata
- Posted at: about 2 months ago
- Author title: Jr. SEO Specialist





## Related discussions
- [How well does Trello scale into a larger team?](https://www.g2.com/discussions/1-how-well-does-trello-scale-into-a-larger-team)
  - Posted at: over 13 years ago
  - Comments: 6
- [Can we please add a new section](https://www.g2.com/discussions/2-can-we-please-add-a-new-section)
  - Posted at: over 13 years ago
  - Comments: 0
- [Quantifiable benefits from implementing your CRM](https://www.g2.com/discussions/quantifiable-benefits-from-implementing-your-crm)
  - Posted at: over 13 years ago
  - Comments: 4