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
In our project we were using image: docksal/ci-agent:edge-php which uses latest development version. And with recent docksal image release docksal/ci-agent v1.11.0 switches Composer version from v1 to v2 in the php flavor of the image. This created a problem with our project build and Drush unable to detect aliaseswhen doing acquia deployments.
Errors:
Source build error
source build-env
bash: build-env: No such file or directory
Drush Could not find the alias @myproject.test.platform
What i observed was drush could not find alias was because of my project was using Composer v1 but docksal/ci-agent v1.11.0 release uses composer v2 this created an issue.
Temporary Workaround : Pinning image version to the previous stable release (1.10) instead of edge (which points to the dev version):image: docksal/ci-agent:1.10-php
Thanks
Manjunath
The text was updated successfully, but these errors were encountered:
In our project we were using image: docksal/ci-agent:edge-php which uses latest development version. And with recent docksal image release docksal/ci-agent v1.11.0 switches Composer version from v1 to v2 in the php flavor of the image. This created a problem with our project build and Drush unable to detect aliaseswhen doing acquia deployments.
Errors:
bash: build-env: No such file or directory
What i observed was drush could not find alias was because of my project was using Composer v1 but docksal/ci-agent v1.11.0 release uses composer v2 this created an issue.
Temporary Workaround : Pinning image version to the previous stable release (1.10) instead of edge (which points to the dev version):image: docksal/ci-agent:1.10-php
Thanks
Manjunath
The text was updated successfully, but these errors were encountered: