Hi @meshfemi,

In my opinion, someone can correct me here of course, deliveries need to be installed in order. It can have impacts especially if the contents of the delivery have the same component. Unless ofcourse you were given the all-okay and that the contents of the delivery are not from the same product area.

Deliveries need to be installed in the order they have received. In a deliver (Specially database, model, and middle tier) we only include the delta (Changed files). So must be in the order to avoid  any dependencies to the previous one. You can only install deliveries by cherry picking if it only have binary files (Example App10 IEE or JSF Binary deliveries). But MWO is not a binary delivery and it’s a Group delivery  (Same as a single patch in terms of the file content).

Thanks you guys for your inputs. 

@kathlk  if you arrive in such a situation, can we fix this by reverting some deliveries and then apply them again? 

Does IFS cloud support a mechanism to revert a delivery?

Hi,

if this is related to APP10, then complexity in reverting a delivery is depends on the content of the delivery. If the deliver only have runtime binaries, then revert means get the old versions and apply another delivery to revert them. But if the delivery had files like model, plsvc and if they are modified file, then deploy old version is enough. But if your delivery had new files, then you will also need to remove them manually from the IFS Home.