You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@streams.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/03/28 14:22:00 UTC
[jira] [Commented] (STREAMS-586) Run docker containers supporting
persist ITs one at a time
[ https://issues.apache.org/jira/browse/STREAMS-586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16417405#comment-16417405 ]
ASF GitHub Bot commented on STREAMS-586:
----------------------------------------
steveblackmon opened a new pull request #424: resolves STREAMS-586
URL: https://github.com/apache/streams/pull/424
now the docker containers lifetime is just the lifecycle of the integration-tests phase for one module.
and integration testing should work regardless of which level of the maven hierarchy it is launched from.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
> Run docker containers supporting persist ITs one at a time
> ----------------------------------------------------------
>
> Key: STREAMS-586
> URL: https://issues.apache.org/jira/browse/STREAMS-586
> Project: Streams
> Issue Type: Improvement
> Reporter: Steve Blackmon
> Assignee: Steve Blackmon
> Priority: Major
>
> The release process as currently documented requires the release manager to start a docker container for every persist module that uses docker, all at once.
> A more sensible strategy would be for each module to start it's own container in pre-integration-test and stop it in post-integration-test.
> It would be nice to have a way keep the containers built during ITs running once testing has concluded.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)