[Travis] Disabled symlinking of local dependency #650
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Example failure:
https://travis-ci.com/github/ezsystems/ezplatform-http-cache/jobs/486034188
Error:
Varnish container fails to builds, because it's not able to find the
vendor/ezsystems/ezplatform-http-cache/docs/varnish/vcl/varnish5.vcl
file.This happens only for builds in ezplatform-http-cache repository and is caused by #648 .
In #648 I've changed the repository type to
path
. This has one unforseen consequence - packages downloaded using that method are symlinked by default (Ref: https://getcomposer.org/doc/05-repositories.md#path)The PR dependency is moved on the host to
/home/travis/build/ezplatform/ezplatform-http-cache
and there is no ezsystems/ezplatform-http-cache in thevendor
directory - there is only a symlink to the actual location.Looks like Docker is unable to resolve (follow) the symlink when trying to copy the file and reports that the file does not exists.
This solution disables symliniking of the dependency -it's mirrored (copied) instead, so that the files are where they are supposed to be and everything works as before.
I've tested the solution on 3.2 with 2 PRs:
#649
ezsystems/ezplatform-http-cache#145
And Varnish container is setup correctly.