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
We run pytest-docker-compose in our CI flow, it works great!
We run our CI on same workloads (same docker engine), if 2 runs are executed simultaneously one will fail because both are getting same docker-compose default project name _default
We would like to have an option to control what will be the project name, in our case we will put there random UUID or Jenkins build number + branch.
The docker-compose flag I refer to is: -p, --project-name NAME Specify an alternate project name (default: directory name)
The text was updated successfully, but these errors were encountered:
barelnir
changed the title
Support docker-compose name rather that default (folder name)
Support docker-compose alternative project name as pytest param
Sep 18, 2020
It looks like line 136 of init.py would be the place to put this - I tried a quick hack, it seems to work - of course, I haven't spent the time to figure out how to make it an option, since I suspect it would kill the ability to use running containers.
I'm interested in this capability in order that I can use pytest-parallel to run my tests on a box with many CPUs and much memory in parallel.
We run pytest-docker-compose in our CI flow, it works great!
We run our CI on same workloads (same docker engine), if 2 runs are executed simultaneously one will fail because both are getting same docker-compose default project name _default
We would like to have an option to control what will be the project name, in our case we will put there random UUID or Jenkins build number + branch.
The docker-compose flag I refer to is:
-p, --project-name NAME Specify an alternate project name (default: directory name)
The text was updated successfully, but these errors were encountered: