Something went wrong on our end
-
Robert Schmidt authored
Since commit 041b2b2d, the CI main loop iterates over all steps, even if there has been a problem during an earlier XML step. In all cases, UndeployObject() is marked to always run, as we always need to make sure that all deployed services are terminated. UndeployObject() always recovers logs. Hence, it's not necessary to do it here as well; it leads to duplicated logs. This is visible in all pipeline with a failed deployment: the logs appear twice.
Robert Schmidt authoredSince commit 041b2b2d, the CI main loop iterates over all steps, even if there has been a problem during an earlier XML step. In all cases, UndeployObject() is marked to always run, as we always need to make sure that all deployed services are terminated. UndeployObject() always recovers logs. Hence, it's not necessary to do it here as well; it leads to duplicated logs. This is visible in all pipeline with a failed deployment: the logs appear twice.