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
The go test code places some files in a folder, say a .bazooka.yml and a couple .go files for example
The test code then starts a git daemon container to serve these files over the git:// protocol. The files directory is bind-mounted to the git container
This works if the test code is executed on the host, but not in bazooka, because the test code places the files in a directory in its own filesystem, which is not visible from the outside and cannot be mounted as a volume in another container.
The text was updated successfully, but these errors were encountered:
I really don't like the idea of specifying host paths in the .bazooka.yml file.
I was thinking of something like:
volumes:
- env_var_name:/a/container/path
Where bazooka would mount a host directory in the container under the specified path, while also exposing an env var with the specified name containing the said host path.
An example:
In the upcoming bazooka e2e (end to end tests):
.bazooka.yml
and a couple.go
files for examplegit://
protocol. The files directory is bind-mounted to the git containerThis works if the test code is executed on the host, but not in bazooka, because the test code places the files in a directory in its own filesystem, which is not visible from the outside and cannot be mounted as a volume in another container.
The text was updated successfully, but these errors were encountered: