Developing with Spryker Code Upgrader

Edit 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 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 PR with the needed updates. Your development team reviews the branch to merge or close it.

The Upgrader doesn’t change existing PRs and creates a new one only after a previous PR was merged or closed.

Following your usual development process, the development team deploys the updates to a staging environment. After passing all quality processes, the development branch propagates into your release branch.

Responsibilities of the development team

Next steps

Prepare a project for the Upgrader