-
Notifications
You must be signed in to change notification settings - Fork 396
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
Build failing on drush alias #101
Comments
Is this is a completely up-to-date version of BLT? There was a bug related to this which was fixed yesterday. |
I had cloned it yesterday a couple time while troubleshooting. I just cloned it again after your response. Same error. :( |
Ok, will try to reproduce. Thanks for filing the issue. |
I was not able to reproduce. @jeffreyisham Can you confirm that the following line is in properties.xml on your local clone of the repo? This is the line that should prevent the error you're getting. https://github.com/acquia/blt/blob/8.x/template/build/core/phing/tasks/properties.xml#L24 |
Confirmed. Spinning up with DrupalVM now to compare. |
Seems similar, but DrupalVM fails on setup here: `Could not find the alias @self [error] BUILD FAILED |
Yeah there are additional setup instructions for DrupalVM which we're still working on. Basically, you need to create a drush alias for the VM and then ensure that it is the default alias by setting |
@jeffreyisham Can you post the entire log output for the command when it is run outside of the VM? |
` project > setup:git-hooks: [delete] Deleting directory /Users/34532/Sites/AcquiaBLT/blted8/.git/hooks project > setup:drupal:settings:
project > setup:behat:
project > setup:composer:install: Gathering patches for root package.
Generating autoload files
project > setup:build:profile:
Loading release_info engine. [notice] project > frontend:install: [property] Loading /Users/34532/Sites/AcquiaBLT/blted8/project.yml project > frontend:install:run: project > frontend:build: [property] Loading /Users/34532/Sites/AcquiaBLT/blted8/project.yml project > frontend:install: [property] Loading /Users/34532/Sites/AcquiaBLT/blted8/project.yml project > frontend:install:run: project > frontend:build:run: project > setup:build:all: project > setup:drupal:install:
Executing: mysql --defaults-extra-file=/private/tmp/drush_DIDuVI --database=blted8 --host=127.0.0.1 --port=33067 --silent < /private/tmp/drush_HXgcUc > /dev/null BUILD FAILED Total time: 2 minutes 55.44 seconds |
Oh! Ok, that's failing much differently that I expected. Seems like an issue with the configuration being imported. What's your |
|
Are you only using Drupal VM? Or are you also trying to use this with a native LAMP stack? I've tried to replicate your problem with Drupal VM, and in the process I updated the documentation in #104. Perhaps updating your configuration to match the new instructions would solve your problem. |
Sorry I should have been more clear... The config settings and initially reported issue are in regards to using it with dev desktop providing the LAMP stack. I attempted setting up Drupal VM as more of a troubleshooting step to see if I encountered the same issue. We have developers on staff who might use either. I don't really have a preference personally. I'd like to focus on getting it to work with dev desktop first as that is the lowest barrier for entry. |
Noticed in the latest batch of changes, the instructions echoed out at the end of ./blt.sh create now have you run ./blt.sh local:setup rather than just setup. It still fails in the same way though. |
I didn't dig into the entirety of the code checked in yesterday, but the issue is now resolved. |
Don't know if there were any relevant code changes when you changed bolt to BLT, but with a fresh clone of the repo, when I run ./blt.sh setup my build is now failing on setup.xml line 80. I'm not quite sure how to resolve. I am using dev desktop for my local environment.
BUILD FAILED /Users/34532/Sites/AcquiaBolt/olson-blt/build/core/phing/tasks/setup.xml:80:32: Drush exited with code 75
The text was updated successfully, but these errors were encountered: