Spryker Code Upgrader in a development workflowEdit on GitHub
Spryker Code Upgrader works best when it is strategically integrated into your development process. This document describes how to integrate the Upgrader into your Scrum activities and Git flow to help streamline and optimize the development workflow.
Processing code upgrades with Scrum
When the Upgrader is integrated into your development process, we recommend processing updates during the following scrum activities:
Sprint planning: review, prioritize, and select the upgrade suggestions to be installed in the upcoming sprint.
Sprint execution: review, validate, modify, and merge the upgrades using the Git flow.
This approach lets you break up big upgrades into smaller pieces. Each smaller piece can be processed within a sprint ensuring the continuity of the process.
Git flow for code upgrades
The Upgrader connects to a selected base branch in your project’s repository, like a Development branch. Based on the defined schedule, the Upgrader pulls the branch, analyzes the code and creates a pull request with the needed updates. Your development team reviews the branch to merge or close it. For processing the PRs, you can use the process described in Processing code upgrades with Scrum.
The Upgrader creates a PR only after a previous PR was merged or closed.
Following your standard development process, the updates are deployed to a staging environment. After passing all quality processes, the Development branch propagates into your release branch where it gets deployed to production.
Development team responsibilities
Prepare your project for the Upgrader.
Connect the Upgrader of Spryker Code Upgrader with your code hosting service.
Cover customizations with automated tests.
Extend development process with additional guidelines and quality checks.
Regularly process upgrade suggestions.
For submitting the form