While CI tools can run test on every pull request when it's opened, and on every branch after it's pushed, it may not be sufficient to avoid broken builds.
For instance, if you have two pull requests that modify dependent code, the tests could pass on each pull request independently and Github would allow the merge but the build may break after the merge.
You may configure Github to block pull request that is not up-to-date with master to avoid this issue. But this may not scale with your team. This configuration means every individual engineer has to:
Takes less than 10 minutes to configure the queue
Adapt to your needs, setup your custom rules
Keep a tab on your builds and merges. Know your star developers.
Whether you use CircleCI, Jenkins, TravisCI or any other tools
No more merge wars, all pull requests get processed orderly.
We are happy to help setup the configuration for you, if you need help.
SOC 2 is a deep-dive audit, delivered in a final report, based on AICPA’s existing Trust Services principles and criteria. MergeQueue has completed SOC 2 audit evaluated on information systems relevant to security, availability and confidentiality.
If your organization requires something more than SOC 2, MergeQueue offers Single Tenant instances of our platform. The goal with our Single Tenant solution is to give you a SaaS-like experience, except your resources and liabilities are not shared with other tenants. Your data at rest remains isolated and more secure.
For the businesses in highly regulated industries, or the ones running Github Enterprise on their own cloud provider, MergeQueue also offers on-premise installation of our platform. We use docker compose bundle with a single installation script to provision the platform. Contact firstname.lastname@example.org for details.