Currently, if running multiple migrations, when one migration reports any failure, the entire process stops with that migration and subsequent migrations are not run. That's not necessarily desirable, especially when developing a set of migrations where you'd like it to run the whole thing and gather all the errors from all the migrations rather than have to identify and fix them one at a time. So, I propose a --continue-on-failure
option to the migrate-import
command, which will run all selected migrations whether or not one in the middle fails.
I've done this in the context of my current project, I need to generate a patch against dev.
Comment | File | Size | Author |
---|---|---|---|
#11 | 3092369-migrate_tools-drush8.patch | 3.92 KB | agentrickard |
#5 | 3092369-5.patch | 10.42 KB | heddn |
#5 | interdiff_4-5.txt | 2.91 KB | heddn |
Comments
Comment #2
mikeryanI had trouble getting DrushCommandsTest to run locally, let's see how the testbot does...
Comment #3
heddnIt seems to be missing a few places. And this will too. But it seems closer.
Comment #4
heddnMissed uploading the patch and interdiff last night. But here's everything; and it passes on local. Let's see what the testbot thinks.
Comment #5
heddnSeems we need to add the continue-on-failure option to migrate:status as well. Which makes sense. This does that and adds some more test coverage.
Comment #6
mikeryanAh, nice improvements - thanks @heddn!
Comment #7
heddnI'll take that as RTBC.
Comment #8
heddnComment #10
heddnComment #11
agentrickardAnd a patch for Drush 8, which needs review, but I'm not going to change status for it.
Comment #13
LendudeLate to the party, but thanks SOOOO much for this! Made my day :)