We have about 600MB database and 33GB files on a Drupal 9 site on Pantheon. The first run of creating a multidev, we get an error on the "Commit code to Pantheon and Push to Pantheon"
remote:
remote: PANTHEON NOTICE:
remote:
remote: Skipping code sync, no Multidev environments were found for branch "pr-310".
remote:
[notice] Creating multidev pr-310 for site ******************
The workaround is to re-run the workflow and it will pass. Only the first time run when PR is created we get this error.
I am assuming this is a timeout on cloning large content to the multidev in the terminus -n build:env:create "$TERMINUS_SITE.live" "$TERMINUS_ENV" --yes $CLONE_CONTENT --message="CI: $COMMIT_MSG" . This step takes about 10 mins to run and then timeout.
Is there a way to not clone files and only clone database (add --db-only as a parameter) to the multidev? I am thinking that we can use stage file proxy module for the files.
We have about 600MB database and 33GB files on a Drupal 9 site on Pantheon. The first run of creating a multidev, we get an error on the "Commit code to Pantheon and Push to Pantheon"
The workaround is to re-run the workflow and it will pass. Only the first time run when PR is created we get this error.
I am assuming this is a timeout on cloning large content to the multidev in the
terminus -n build:env:create "$TERMINUS_SITE.live" "$TERMINUS_ENV" --yes $CLONE_CONTENT --message="CI: $COMMIT_MSG". This step takes about 10 mins to run and then timeout.Is there a way to not clone files and only clone database (add --db-only as a parameter) to the multidev? I am thinking that we can use stage file proxy module for the files.