Skip to content
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

Support docker-compose alternative project name as pytest param #66

Open
barelnir opened this issue Sep 18, 2020 · 1 comment
Open

Support docker-compose alternative project name as pytest param #66

barelnir opened this issue Sep 18, 2020 · 1 comment

Comments

@barelnir
Copy link

barelnir commented Sep 18, 2020

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)

@barelnir 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
@jnawk
Copy link

jnawk commented Dec 11, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants