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

924: Add docker compose support for --build and --rmi options #1336

Closed
wants to merge 5 commits into from

Conversation

sonerd
Copy link
Contributor

@sonerd sonerd commented Mar 24, 2019

Took the changes made here #924

and added test for docker-compose --build

@rnorth
Copy link
Member

rnorth commented Apr 8, 2019

Thank you @sonerd - thanks for being proactive and picking this up from #924.
I'll review and hopefully merge soon.

@rnorth rnorth self-assigned this Apr 8, 2019
public DockerComposeContainer environment = new DockerComposeContainer(new File("src/test/resources/compose-test.yml"))
.withExposedService("redis_1", REDIS_PORT)
.withExposedService("db_1", 3306)
.withBuild(true)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there anything we can do to actually verify the build and remove options work?

As it is, it seems that we’ll get a failure if the build feature throws an exception, but otherwise there’s no verification.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not so into the internals of Testcontainers nur one thing which came into my mind was to verify if the image was build freshly by checking the modifcation date of the file? Would this be an option?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could check for the creation date of the image.

@stale
Copy link

stale bot commented Jul 14, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe this is a mistake, please reply to this comment to keep it open. If there isn't one already, a PR to fix or at least reproduce the problem in a test case will always help us get back on track to tackle this.

@stale stale bot added the stale label Jul 14, 2019
@bsideup bsideup removed the stale label Jul 16, 2019
@rnorth
Copy link
Member

rnorth commented Jul 17, 2019

I've just resolved some merge conflicts and pushed to your fork, @sonerd.

@rnorth
Copy link
Member

rnorth commented Jul 18, 2019

I look into those failures tonight

@rnorth
Copy link
Member

rnorth commented Jul 18, 2019

I need to make tweaks beyond the original merge from master, and can't write to your repository, so I have created a new branch and PR (#1625). I'll continue on that PR so that we can merge!

@rnorth rnorth closed this Jul 18, 2019
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

Successfully merging this pull request may close these issues.

None yet

4 participants