Use Case: Accelerate Releases with Auto-Merge and Digital Sign-Offs

[#1]

Hi Everyone! 

We thought it would be fun to start a bit of a use case series where we highlight the features and functionalities of some of our apps and how enterprises in the DevOps space could find it useful. Would love to hear what you think! 

First up, let me introduce you to our app Workzone (Cloud & Datacenter) - and how you can automate Pull Request merges on build success and digital signature approval. Helping you speed up delivery without sacrificing compliance or code quality.

---

For companies with a highly automated release pipeline Workzone auto-merge is an essential feature that ensures pull requests are merged at the earliest possible point in time without compromising the pull request review and approval process, code quality and reliability.

Case 1: Pull requests automatically merged on successful build

Most enterprise release pipelines involve merging, building and deploying code to multiple environments successively. For example a feature release process starts with a pull request from a certain commit on the main branch tagged feature-1-1 to the release branch. Technically this PR does not need a formal review as all changes have already been reviewed before they were merged to the main branch.

Once the pull request from tag feature-1-1 to release is created it would trigger a CI build to make sure the new release passes all tests. All that’s needed now is a successful build result for this pull request, and it can be automatically merged as soon as the build completes successfully.

Why this matters: In order to automate the release process of already approved and reviewed code , no human interaction should be required while making sure reliability and stability of the released code is maintained.

Case 2: Pull requests automatically merged on digital signature approval

In regulated industries such as finance, pharma, med-tech and life-science any deployment still needs a digital sign-off for FDA/ISO-27001 compliance, even though code has already been reviewed, approved and tested before being merged to the main/master branch.

When a pull request from a tagged main branch commit to a release or production branch is created, Workzone will enforce that

1. The build succeeded
2. The merge is gated by a formal digital sign-off

Once the digital sign-off approval is received, Workzone merges the pull request automatically and the release pipeline can progress.

Why this matters: Workzone auto-merge in combination with digital sign-offs enable team in regulated industries to automate and accelerate their release process while conforming with regulatory compliance in their industry.

---

Thanks for tuning in! 

If you found this insightful, you can learn more about Workzone here...

Happy coding, 

Sean

Izymes Team