Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Large Content --db-only #63

Open
Farnoosh63 opened this issue Aug 3, 2022 · 0 comments
Open

Large Content --db-only #63

Farnoosh63 opened this issue Aug 3, 2022 · 0 comments

Comments

@Farnoosh63
Copy link

Farnoosh63 commented Aug 3, 2022

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 ******************

2022-08-03 at 3 35 PM

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.
2022-08-03 at 3 31 PM

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.

@Farnoosh63 Farnoosh63 changed the title Large Content Large Content --db-only Aug 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant