Idea - When lifetime deploy fails on 1 module handle the aftermath better

When lifetime deploy fails on 1 module handle the aftermath better

Out of scope

Lifetime

Usually we deploy several modules/applications at the same time as they are all related or dependent. Sometimes the first module gets a timeout/compilation error, this forces us to wait several hours before the deploy ultimately fails.

It should be very easy to either STOP the deployment completely, or just LEAVE OUT this one single module which is having the issue.

This could also very well be a bug since it wasn't an issue in the prior platform release....

*I already have a ticket open with support where the reply was: "Minimum specs have been increased, so consider an upgrade of some sort". However the ticket is still open and supposedly there is an ongoing investigation.

08 Jun

Daniël Kuhlmann

MVP

Changed the status to

Out of scope

Marked this as out-of-scope. The ideas page is not an escalation channel for topics that need to be resolved through a support case. Please use the available communication and escalation methods of the support case.

09 Jun

Joey Moree

I respectfully disagree, this is clearly something that can be changed in the usage of lifetime, hence I created it as an idea.

Or are you saying that wishing to have lifetime improved is something that could only be done using a support case? (And thus paying more money for better servers?)

09 Jun