Source to standalone deployment script

Details

Description

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.

Jesse Yates
added a comment - 13/Sep/12 18:47 Reopening issue, since its apparently useful. Actually came up yesterday with testing one of the pom changes I made. Can you give it another spin @stack and commit if you like it?

Initially, this was a pretty small test case, though maybe it would make sense to add this check (running locally from the tarball) to the release checklist. If we add it, we should probably roll this script in to make it easier to deal with (also no real way to see usage if its just attached to the jira).

Jesse Yates
added a comment - 07/Sep/12 20:59 Weird that it didn't work...
Initially, this was a pretty small test case, though maybe it would make sense to add this check (running locally from the tarball) to the release checklist. If we add it, we should probably roll this script in to make it easier to deal with (also no real way to see usage if its just attached to the jira).

stack
added a comment - 07/Sep/12 20:54 I did this:
h-24-30:trunk stack$ pwd
/Users/Stack/checkouts/trunk
h-24-30:trunk stack$ ./dev-support/deploy.sh
Maybe we should just leave the script here attached to the issue and if folks start looking for it, we'll point them here. If uptake, commit later?

Jesse Yates
added a comment - 07/Sep/12 05:41 It seemed slightly useful, at least in testing between the source and a real cluster. I've got a new version somewhere that's a bit better - lemme see if I can find it.