-
Notifications
You must be signed in to change notification settings - Fork 25
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
Basic support for custom networks #32
Conversation
I see no test that actually launches the fixtures, I have tested this manually by using the aforementioned docker-compose file with a custom version of the ath |
cc @olivergondza apparently you are the last one merging things here 😁 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No objections. Not sure using EnvVars is the best approach, but whatever works
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure? This will only take effect when the test or harness picks up this PR though, of course.
Consider this lib deprecated in favor of testcontainers.org.
So jenkinsci/docker-fixtures#32 can be used
:thankyou: |
* Update docker-fixtures to 1.11 So jenkinsci/docker-fixtures#32 can be used * Update doc * Temporary revert so I can get a proper test baseline * Restore back fixtures update
This change adds limited support for custom networks in docker-fixtures, allowing for example to launch the ATH with a docker compose file like this one:
Compose file
copiedinspired by @jglick work