What are the Slack Archives?
It’s a history of our time together in the Slack Community! There’s a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.
Because this space is not active, you won’t be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..
Hello We want to upgrade our Spryker version to the latest release. Currently we have the one from l
Hello
We want to upgrade our Spryker version to the latest release. Currently we have the one from last year (201907.0), and there are two major releases since then (202001 and 202009). Do you think it’s ok to upgrade to latest release directly or should we rather do it in parts? (Jarvis tool says that my next target is 202001 release, which implies that I should do it one by one probably)
Comments
-
Hi Hardik,
Since every major feature-update requires some actions to be done, you would need to follow both guides, 202001 and 202009. depending on the amount of project customisations, I would really suggest to do it iteratively feature-by-feature.0 -
Hi Andriy, that makes sense, thanks!
0 -
You can spread Spryker upgrade task between multiple sprints/iterations, to leave some more space for the features that are so important for the business 🙂
0 -
True, hopefully we won’t end up updating many other modules due to dependencies 🙂
0 -
I would also suggest to release feature updates more often, not in a single batch. That is much easier then
0 -
Tests and automated code checks (like phpstan f.e.) are your friends
0 -
Definitely, it won’t be possible to do the upgrade without them 😄
0 -
Hello again Andriy,
so I gave it a try and tried to update only one feature at a time. I started withspryker-feature/spryker-core
because I think that’s the kind of root module for all others. However I ended up in dependency hell.
Upgrading this feature requires updatingspryker/symfony
, which requires updating many other spryker-shop modules like chart-widget, customer-page etc.
And some of these modules are part of other features like customer-page is part ofspryker-feature/customer-account-management
, which requires updatingspryker/shipment
, which is part of another featurespryker-feature/shipment
So basically I think I would end up updating nearly all features at the same time. It’s hard to split this across sprints as you are suggesting, or am I doing this in wrong way?0 -
Hey @U011K6DASBW what happens if you try to add “--update-with-dependencies” command? How many features gets updated at the same time?
0 -
I used this option everytime I ran composer update, it updates many other deps but sometimes I also had to add other feature modules to the update command to resolve conflicts
following are the commands I triedcomposer require spryker-feature/spryker-core:"^202001.0" spryker/symfony:"^3.3.5" spryker-shop/chart-widget:"^0.2.1" --update-with-dependencies composer require spryker-feature/customer-account-management:"^202001.0" spryker-feature/shipment:"^202001.0" spryker/shipments-rest-api:"^1.2.2" --update-with-dependencies
0 -
just running
composer require spryker-feature/spryker-core:"^202001.0" --update-with-dependencies
fails as it can’t resolve deps0 -
if you get too many dependencies as a result, and many features as a result of an update for a single feature, you might try to do the following:
1. Split *features* into *individual modules* they consist of, with locked module versions
2. do the update on individual modules, iteratively (dependencies is still the case, but not on “big feature level”), as we discussed above until you get everything up-to-date;
3. After update is done, you can replace modules back to features. With latest modules you have it won’t be an issue.0 -
we use this process for quite outdated projects and it works fine. Before suggesting it, I wanted to make sure you can’t do your update purely on the feature level.
0 -
okay, that is a good idea, I will try that 👍
0
Categories
- All Categories
- 42 Getting Started & Guidelines
- 7 Getting Started in the Community
- 8 Additional Resources
- 7 Community Ideas and Feedback
- 75 Spryker News
- 924 Developer Corner
- 783 Spryker Development
- 88 Spryker Dev Environment
- 362 Spryker Releases
- 3 Oryx frontend framework
- 35 Propel ORM
- 68 Community Projects
- 3 Community Ideation Board
- 30 Hackathon
- 3 PHP Bridge
- 6 Gacela Project
- 25 Job Opportunities
- 3.2K 📜 Slack Archives
- 116 Academy
- 5 Business Users
- 370 Docker
- 551 Slack General
- 2K Help
- 75 Knowledge Sharing
- 6 Random Stuff
- 4 Code Testing
- 32 Product & Business Questions
- 70 Spryker Safari Questions
- 50 Random