[ https://issues.apache.org/jira/browse/BOOKKEEPER-788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14194727#comment-14194727 ]
Ivan Kelly commented on BOOKKEEPER-788: --------------------------------------- [~jiannan] [~fpj] I was referring to the QA scripts, bin/test-*. Jiannan, I don't have any automated scripts for testing perf, since it means spinning up a cluster. > 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)