Open jessepinho opened 10 years ago
This makes a lot of sense and should be something we can support.
There's currently under-the hood work in progress on the platform that should improve our tooling around tracking the status of individual jobs.
We'll definitely that this as a valid feature request. Thanks for sharing your use-case!
+1 on this. Getting downstream db pulls scripted in synchronous shell scripts is an absolute must for any professional Drupal CI environment.
Looking forward to this rolling out.
this is related to issue https://github.com/pantheon-systems/terminus/issues/143
When I deploy code, my process looks like the following:
drush psite-uuid my-site
live testdrush psite-uuid my-site
livedrush psite-uuid my-site
test --updatedrush psite-uuid my-site
live --updateI'd love to write a script that does all of this for me in this order. The problem is, commands like
drush psite-clone
initiate the cloning job and then exit, which means a script that does all of the above could theoretically deploy to my live environment before the cloning/backing up/testing/etc. have actually completed. Would it be possible for there to be an option like--no-async
where a command does not exit until the backup/etc. has actually been completed? And it should return an error code if the job fails, so that the next step wouldn't ever get executed (the commands in my script would be chained together with&&
).