[jira] [Commented] (BOOKKEEPER-788) Provide release inspector script

["Flavio Junqueira (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BOOKKEEPER-788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14193770#comment-14193770 ] 

Flavio Junqueira commented on BOOKKEEPER-788:
---------------------------------------------

I like the idea of the script. I'm also not sure what [~ikelly] means with integrating with the buildscripts. Is it about QA or maven build?

The build of hedwig-protocol fails for me when running your script against trunk and it doesn't complete the initialization.

I also noticed that it doesn't spit out an error message, so I had to look at the logs to see what happened. It is not a big deal, but it would be nice to spit out success or failure at the end.

A simple performance test is this:

{noformat}
bookkeeper-benchmark/bin/benchmark bookie -zookeeper <zk> -host <bookie>
{noformat}

> Provide release inspector script
> --------------------------------
>
>                 Key: BOOKKEEPER-788
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-788
>             Project: Bookkeeper
>          Issue Type: Improvement
>            Reporter: Jiannan Wang
>            Assignee: Jiannan Wang
>            Priority: Trivial
>             Fix For: 4.4.0
>
>         Attachments: BOOKKEEPER-788.patch
>
>
> For each release, we need to type a sequence of commands to validate release candidate tag. This process could be achieved by a single script.
> Here is the behavior of the script in my mind:
>    1. Collecting build environment info (Operation System, JDK, Maven)
>    2. Run 'mvn install -DskipTests'
>    3. Checking code (findbugs, rat).
>    4. Running unit test
>    5. Start standalone Bookie and Hedwig service
>    6. Run simple Bookie test: bookkeeper-server/bin/bookkeeper simpletest
> -ensemble 3 -writeQuorum 3
>    7. Run simple Hedwig test: hedwig-server/bin/hedwig console; pubsub
> topic subscriber 10 message
>    8. Tar all above logs when error/exit
> In addition, this script could also be provided to user which could collect related information to diagnose compile/UT failure issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)