Test Updates

[Bruce - PhosphorMedia]

Maybe this exists, but would be handing to have a "Test Update" feature that runs through a test mode of the update to determine at least: What modules need to be updated / removed. There's room in that feature to possible identify other 'potential' issues. But being able to just highlight modules that are problematic would be great.

[lesliekirk]

Maybe this exists, but would be handing to have a "Test Update" feature that runs through a test mode of the update to determine at least: What modules need to be updated / removed. There's room in that feature to possible identify other 'potential' issues. But being able to just highlight modules that are problematic would be great.

I always wondered how the conflicts and "stops" are pointed out. It would be handy to have something other than a dev site to break the updates on. Seems even with a dev site though something still gets through. I get that it's hard to test all of the variables out there.

[Brennan]

Today we have an upgrade advisor where we manually prevent the update for someone on a certain version of a module where we find an issue with. These warnings come from us testing new releases against difference test instances.

Before we install any new updates we also validate each module version is the version we expect it to be.

We're always looking for new ways to make the update process smoother, but today you can get what you're looking for by running the updates on a copy of the store before running them on production.

[ids]

One thing I've never been clear on, will the update run through all the potential conflicts before actually applying the update? Regardless of that answer, the enigma is that you find out about the conflicts while attempting to perform the streaming update. It seems inefficient because you have to fix the current conflict before you can move on to the next one and you don't know what that will be. I'd like to know from the advisor all the potential issues before running the update. I think it would be good if that result could be emailed or at least stored in a file or table, etc.

Scott

[Bruce - PhosphorMedia]

What Scott said...that's what i was getting at. Also, we are trying to avoid always having to create a dev site as that adds to the time and hosting load.

Can you publish the list of module versions? It would be rather simple to create a tool that compares current modules to that list.