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

Stop container by container name #190

Open
thjaeckle opened this issue Jun 10, 2015 · 3 comments
Open

Stop container by container name #190

thjaeckle opened this issue Jun 10, 2015 · 3 comments

Comments

@thjaeckle
Copy link

First of all: Thanks for the awesome Docker Maven plugin - we use it for integration and performance tests and the linking, cleanup, etc. works just great.

We would like to use it as well for running the "latest and greatest" of our containers and do so in a nightly Jenkins job.
The plugin almost provides everything for that:

  • namingStrategy: alias
  • fixed port mappings

The only thing which is missing would be to stop containers by their container name.
docker:stop would therefore need another parameter:
containerNameToStop (or similar)

Is that possible?

@computerlyrik
Copy link
Contributor

How about using a extra pom or profile for integration servers?

I can see inside the documentation the remove and build targets can be manipulated global .

@jgangemi
Copy link
Collaborator

jgangemi commented Jul 9, 2015

a profile may or may not help in this case, it depends on if you have other container definitions and how they are managed in the overall pom. see issue #207.

what's the use case for this? how do you see the jenkins job working?

@fpt-thanhdq2
Copy link

how do I define the docker stop in the pom.xml file?
currently i need to run in command line : mvn docker:stop

leusonmario pushed a commit to leusonmario/docker-maven-plugin that referenced this issue Aug 18, 2018
Added badge for plugin version
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

4 participants