Abort remaining on failure

General
1

Currently we have the very nice feature where if sub-deployment A fails, then sub-deployment B, will be aborted and everything is left as it was. This is vital when A is a complete replacement of data. Ah, but in my “reverse migration” / “refresh staging” model, I’ve noticed that dealing with our client’s 200GB’s of 53 files that it doesn’t work… :frowning:

However, I have discovered that I can break up the refresh into multiple parts, and it does work :slight_smile: I even tested the four biggest files together (about 120GB) and that worked.

So my feature request is for a way to apply “Abort Remaining” to distinct pairs. That way one could do the following

Sub 1: Pull Group A build off Production
Sub 2: Migrate clones from staging build A

Sub 3: Pull Group B build off production
Sub 4: Migrate clones from staging build B

Sub 5: Pull Group C build off production
Sub 6: Migrate clones from staging build C

—Bob’s your uncle.

Of course this can be done in one migration with six sub-deployments, but if something goes wrong with one migration set, I still want to keep the others. So, an “oopsies” occurs with Group group B data, then abort Sub Deployment 4, move on to the Group C. Post deployment, we can troubleshoot Group B, without loosing all the time already invested.

This may be an edge case, but I thought it worth a suggestion.

2

Hey Fred,

That is an interesting idea. I think your use case may be covered by one of our next big things for OttoDeploy, which is the ability to group deployments and run them in sequence. It would essentially let you group the sub-deployments into separate deployments based on what you want to abort remaining based off of. Then these would run in series like they do with sub-deployments, but as separate deployments. Does that sound like what you’re looking for?

-Kyle

3

That sounds exactly like what I am asking for. Looking forward to seeing how it works. My next big challenge is to see what it will take to get the FMDeveleoperTool to rename all 53 files. So far that has not been successful, but that’s not yet any OttoDeploy feature. :wink:

1 Like