Use Case - Workzone
Continuous Integration and Deployment with Automated Merge Control
Enforce TDD discipline and regulatory-grade release control by merging only after builds pass — no manual steps, just proven code flow.
Use Case
Continuous Integration and Deployment with Automated Merge Control
A large number of enterprises have adopted Continuous Integration and Deployment as part of their agile development practice. Automated tests and builds are essential to ensuring code quality and maintaining confidence as changes move through environments. But enterprise teams also need guardrails to ensure that code only flows forward when it’s proven—not just written.
Workzone’s integration with CI systems and support for automated merging based on build results enables a high-confidence release flow without unnecessary manual bottlenecks.
Example: Enforcing a CI-Driven Promotion Pipeline
Let’s walk through an example from a medical device company with three primary branches:
- feature/* → for new features and fixes
- develop → the integration branch for QA
- master → the release-ready production branch
Step 1: User-Driven Review and Approval for Features
Engineers submit pull requests from feature/* to develop. These are reviewed by assigned teams with reviewer quotas and digital signatures configured for compliance.
Configuration:
- feature/* → develop:
- Reviewer group quota: groupQuota[‘frontend’] >= 1 & groupQuota[‘backend’] >= 1
- Digital signatures required: requiredSignaturesCount >= 2
- Build check: requiredBuildsCount >= 1
- Merge: Manual or automatic after compliance
Step 2: Auto-Merge from develop to master — Build-Driven
Once develop has accumulated approved and signed changes, the pull request to master is created. But unlike earlier steps, this is CI-gated — not people-gated. No human review is required at this stage. The requirement is that the full CI pipeline passes successfully.
Configuration:
- develop → master:
- No reviewer quotas
- No manual approvals
- Watch Build Result: ✅ Enabled
- requiredBuildsCount >= 1
- Auto-merge user: release-bot (Write access only to master)
Supported CI Systems
Workzone listens for build notifications from supported CI tools using the Bitbucket Build REST API:
Jenkins
- Install Bitbucket Notifier Plugin
- Configure plan with Bitbucket base URL and credentials
- Supported auth: Basic Auth
- On success: Jenkins sends a build success notification → Workzone merges the pull request
Bamboo
- Set up an Application Link between Bamboo and Bitbucket
- Build results are automatically pushed
- Supported auth: OAuth or Basic Auth
- On success: Workzone detects the build status and merges automatically
Other CI tools
Any CI/CD platform capable of making Bitbucket Build Notification API calls can be used with Workzone.
Benefits for Enterprise DevOps Teams
| Benefit | Description |
|---|---|
| CI-gated promotion | Eliminate the risk of untested code reaching production branches |
| No human bottlenecks | Avoid delays during handover from QA to production |
| Enforce TDD rigor | Ensure all tests pass before merge—no exceptions |
| GitOps compatibility | Automate production readiness using Git as the source of truth |
| Regulatory alignment | In regulated sectors, this enforces validated handoff to release branches |
Use Cases
Explore More Use Cases...
Learn how enterprise teams streamline workflows, boost compliance, and drive productivity with Izymes apps
