[jira] [Resolved] (HBASE-5354) Source to standalone deployment script

2015-10-28 Thread Jesse Yates (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-5354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jesse Yates resolved HBASE-5354.

Resolution: Won't Fix

Seems like this is covered by the docker image. Probably needs updating if 
someone wants to pick this up later

> 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-v0.patch, bash_HBASE-5354-v1.patch, 
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Resolved] (HBASE-5354) Source to standalone deployment script

2012-09-04 Thread Jesse Yates (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-5354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jesse Yates resolved HBASE-5354.


Resolution: Won't Fix

No one really seems to need this, particularly with being able to run from the 
source. Dropping it.

 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