Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 7 Sep 2012 16:50:08 +1100 (NCT)
From: "Jesse Yates (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <1965751676.48818.1346997008697.JavaMail.jiratomcat@arcas>
In-Reply-To: 
 <1270994186.15823.1328726820965.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-5354) Source to standalone deployment
 script
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jesse Yates commented on HBASE-5354:
------------------------------------

there were some things I added later that made it a bit nicer - give me a day or so.
                
> Source to standalone deployment script
> --------------------------------------
>
>                 Key: HBASE-5354
>                 URL: https://issues.apache.org/jira/browse/HBASE-5354
>             Project: HBase
>          Issue Type: New Feature
>          Components: build, scripts
>    Affects Versions: 0.94.0
>            Reporter: Jesse Yates
>            Assignee: Jesse Yates
>            Priority: Minor
>         Attachments: bash_HBASE-5354.patch
>
>
> Automating the testing of source code in a 'real' instance can be a bit of a pain, even getting it into standalone mode.
> Steps you need to go through:
> 1) Build the project
> 2) Copy it to the deployment directory
> 3) Shutdown the current cluster (if it is running)
> 4) Untar the tar
> 5) Update the configs to point to a local data cluster
> 6) Startup the new deployment
> Yeah, its not super difficult, but it would be nice to just have a script to make it button push easy.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira