ChaRM - Multiple Maintenance Cycles

[Former Member]

We now have a Quarterly release cycle; however, we'd also like to have a Weekly release cycle for the smaller break / fix changes that are not true Urgents. We don't want to use UCs for these since we'd like to move them together on Saturday morning. How can we prevent leapfrog issues? For example, if an object is on the Quarterly and Successful Testing is recorded, the object is released. If the the same object is now changed and included on the Weekly Maint Cycle and moved to production, it will be overlaid when the Quarterly Maint Cycle is moved to production. I don't think this is possible, but I was asked to confirm..... Is it possible to re-import all of the Transports from previous weeks at the time the Quarterly ones are moved to ensure all Transports are moved in the order they were actually released? Is there a way to detect / prevent leapfrog issues? What do other companies do?

[Former Member · Accepted solution]

If you use normal correction for your quarterly release and SDHF corrections for your weekly releases, the normal correction will move ALL transports for the maintenance project including those which are for the SDHF corrections and even those for which the SDHF correction has not been approved for production import.

If you are only using SDHF variants for your process - then there is a possibility to handle this manually through the maintenance cycle directly. There are mass transport move tasks in the task list of the maintenance projects. However, this will require a manual element to your process for the production import.

But as you may already be aware, either of these options are tricky to implement and you need to have someone with a good understanding of development and transports.

Hope this helps...

Cheers

Pranav