Enforcing Workzone merge conditions on all levels
Workzone doesn’t stop users merging pull requests manually by clicking the ‘Merge’ button. However, if merge conditions are to be enforced this can be enabled in Workzone’s global settings, project and or repository settings. The most specific setting will be applied.
Configuring pull request list columns in Organizr
Organizr allows Bitbucket (server) administrators to configure which columns are displayed and how wide they are. Columns such as 'Labels', 'Due date', 'Description' etc can be enabled or disabled and a column width can be specified. Global pull request page Global Bitbucket
Counting approvals – Finally
I don't know why it took us so long to make counting the number of approvals for a pull request available in Workzone. Finally Workozone allows you to create merge conditions with an 'approvalCount'. Workzone now supports absolute pull request reviewer approval counts
Adding specific pull request reviewers for different parts of your codebase
TL;DR Specifying include and exclude file/path patterns for pull request reviewers with Workzone makes sure that specialised teams only need to review 'their' code changes. This saves them time and reduces the pull request noise level. Too many PR reviews, every day
Organizr enhanced search – so much faster now!
Organizr for Bitbucket v3.1.0 features massive performance improvements for larger instances with lots of pull requests. We have fundamentally changed the way pull requests are searched for. Organizr no longer sifts through an endless pull request list (in larger instances) and
Workzone Project Settings – Here we go
Bitbucket Server 5.2 brought us project-wide settings for most configurable features. Now the shiny new version 5.5.0 of Workzone for Bitbucket has project-wide settings for Hooks Reviewers Digital Signature Approvals (Auto) Merge Conditions Caveat: Workzone project configurations won't let you select
A (very) Simple Template Renderer for Java
When we introduced customisable email subjects for Reminders for Bitbucket I needed a template renderer that takes a user-defined string based template references template placeholders and resolves their values in the render context does not depend on any heavy weight templating
Workzone Advanced Merge Conditions with Specific Group Quota
Advanced Merge Conditions with groupQuota are an important part of Workzone's merge-control features. Let's recap on advanced merge conditions: A boolean expression describes the merge condition in a clear and concise way. Using tokens like approvalQuota, groupQuota, requiredSignaturesCount, requiredBuildsCount an advanced merge condition could be
How to do test-driven development with merge control and continuous integration
Test Driven Development (TDD) is best practice and the chosen software development process for companies that take their code seriously. But what about test-driven merge control? Wouldn't it be nice to make a pull request merge depend on successful test results
From simple to advanced control of merge conditions
Workzone's automated pull request merge control is easy and straightforward to configure by defining some simple merge conditions: For a simple merge condition all or a subset of the following criteria are AND combined to allow a merge to happen or block