[
https://issues.apache.org/jira/browse/HDDS-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16834164#comment-16834164
]
Eric Yang commented on HDDS-1458:
---------------------------------
{quote}Not exactly, I am talking about a differnt thing. Let's imagine that you
start two build paralell. How do you know which image is used to execute the
tests? You can't be sure. There is no direct relation ship between checked out
source code, docker image which is created and the compose files. (We need
build specific tag names for that which are saved to somewhere).{quote}
This can be done by using:
{code}
mvn -Dversion=[customized_version]
{code}
This property will be materialized via maven resource plugin of Dockerfile with
customized version. Hence, each build generates a unique version number that
is identical between jar, tar, and docker image. Post build will need to have
a clean up script to delete old Docker images. I think this may have already
been done in most projects on Jenkins.
{quote}BTW, the original question (how the blockade/fault injection tests can
be executed as part of the maven build) can be solved easily (IMHO). I uploaded
the patch to demonstrate it.{quote}
I don't see your patch in this issue. Where did you upload the patch?
>From today's Ozone meeting, we agree on making sure that fault injection test
>can work with docker image that carry ozone binaries, and docker image that
>mount ozone binaries. This ensure that the current work flow is not
>disrupted. I will update patch to reflect this agreement.
> Create a maven profile to run fault injection tests
> ---------------------------------------------------
>
> Key: HDDS-1458
> URL: https://issues.apache.org/jira/browse/HDDS-1458
> Project: Hadoop Distributed Data Store
> Issue Type: Test
> Reporter: Eric Yang
> Assignee: Eric Yang
> Priority: Major
> Attachments: HDDS-1458.001.patch, HDDS-1458.002.patch,
> HDDS-1458.003.patch
>
>
> Some fault injection tests have been written using blockade. It would be
> nice to have ability to start docker compose and exercise the blockade test
> cases against Ozone docker containers, and generate reports. This is
> optional integration tests to catch race conditions and fault tolerance
> defects.
> We can introduce a profile with id: it (short for integration tests). This
> will launch docker compose via maven-exec-plugin and run blockade to simulate
> container failures and timeout.
> Usage command:
> {code}
> mvn clean verify -Pit
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
