You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of our CI setup, we run something like this:
if curl -s --head --request GET http://$CIRCLE_BRANCH-$PANTHEON_SITE_NAME.gotpantheon.com | grep "404 Unknown site!" > /dev/null; then
drush pantheon-site-environment-create $PANTHEON_SITE_UUID $CIRCLE_BRANCH --source=$PANTHEON_SOURCE
drush pantheon-site-environment-lock $SITE_UUID $CIRCLE_BRANCH $PANTHEON_ENV_USERNAME $PANTHEON_ENV_PASSWORD
else
drush pantheon-site-clone $PANTHEON_SITE_UUID $PANTHEON_SOURCE $CIRCLE_BRANCH --db -y
fi
We are checking wether an environment already exists for the branch and if not we create it. If it does already exists we clone a fresh database onto it.
In the case where we create the environment using pantheon-site-environment-create the process waits until the environment has actually been created before moving on - which is what we want.
However, in the case pantheon-site-clone the process ends immediately, before pantheon actually cloned the environment. The problem with this is any any attempts to run commands or tests against the freshly cloned environment fail, as the database is still in the process of being created.
Any way to get psite-clone to work in the same way as psite-ecreate (in the foreground)?
The text was updated successfully, but these errors were encountered:
This is definitely possible, and will become even easier with some of the behind the scenes changes that are being done to make it simpler and more precise to externally track individual job status.
In the short term it's feasible to add a call in to terminus_job_poll():
As part of our CI setup, we run something like this:
We are checking wether an environment already exists for the branch and if not we create it. If it does already exists we clone a fresh database onto it.
In the case where we create the environment using pantheon-site-environment-create the process waits until the environment has actually been created before moving on - which is what we want.
However, in the case pantheon-site-clone the process ends immediately, before pantheon actually cloned the environment. The problem with this is any any attempts to run commands or tests against the freshly cloned environment fail, as the database is still in the process of being created.
Any way to get psite-clone to work in the same way as psite-ecreate (in the foreground)?
The text was updated successfully, but these errors were encountered: