[
https://issues.apache.org/jira/browse/WHIRR-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White updated WHIRR-152:
----------------------------
Attachment: WHIRR-152.patch
Here's a partial patch for this (needs filling out for services other than
Hadoop). Set the property whirr.test.keep-cluster-on-failure to true to leave
the cluster running if the test fails. E.g.
{code}
mvn verify -Pintegration -DargLine="-Dwhirr.test.provider=ec2
-Dwhirr.test.identity=$AWS_ACCESS_KEY_ID
-Dwhirr.test.credential=$AWS_SECRET_ACCESS_KEY
-Dwhirr.test.keep-cluster-on-failure=true"
{code}
Shut it down later with the DestroyTestClusters test. E.g.
{code}
mvn verify -Pintegration -DargLine="-Dwhirr.test.provider=ec2
-Dwhirr.test.identity=$AWS_ACCESS_KEY_ID
-Dwhirr.test.credential=$AWS_SECRET_ACCESS_KEY" -Dit.test=DestroyTestClusters
{code}
> Add option to leave cluster running when integration tests fail
> ---------------------------------------------------------------
>
> Key: WHIRR-152
> URL: https://issues.apache.org/jira/browse/WHIRR-152
> Project: Whirr
> Issue Type: Improvement
> Components: core
> Reporter: Tom White
> Attachments: WHIRR-152.patch
>
>
> This would be useful for debugging why tests failed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
