Ticket #2412 (new enhancement)

Opened 8 years ago

Repeated walks during upgrade steps

Reported by: gracinet Owned by: gracinet
Priority: P2 Milestone: CPS 3.5.7
Component: CPSDefault Version: 3.5.2
Severity: normal Keywords: upgrade step walk
Cc:

Description

Lots of upgrade steps have to walk either the whole document repository or the whole site structure. In case of big version bumps, this may make the process too long, especially for big real life installations for which the admins may want to check the upgrade on a regular basis during validation time.

Although a generic and fully automated solution is a bit tough, there is already a workaround for this very same problem : CPSDefault's upgrade_unicode job : instead of calling the upgrade steps, it handles the walks and call the inner part of the steps. It could be extended and maintained as a big "do they all at once" upgrade job.

Ideally, that would be with more knowledge gathered from the step metadata :

  • a notion of "inner step"
  • a type of walk (repository, folders…)

But in the short term, simply knowing from that code about major existing steps and how they behave would be good enough.

Note: See TracTickets for help on using tickets.