· Fetches the code from Git source code repository.
· Build the code (tar) and put it in the build server.
· Triggers the deployment jobs.
· Copy the build package to the remote deployment server.
· Un tar the build package.
· Tag the release version.
· Stop app
· Link the release version to the application folder. (Deploy application)
· Start app
· Maintains 3 release versions in the target deployment server. (So that we can rollback to previous version of the code, if required.
Please suggest if we have any specific build process for rails app. Currently I am just using tar.
yes, thats more of a deployment tool. I am able to deploy my rails app in a continuos manner right now. I just want to know if my approach is rite and if there is any specific build techniques for rails app. Currently, I just pull the source code from repo --> tar it into a package--> stop app in target ---> untar the package in target (and some other release versioning stuff) using ansible --> start the app.
Thanks,Vivek
On Wednesday, 26 October 2016 04:04:05 UTC+5:30, Hassan Schroeder wrote:On Tue, Oct 25, 2016 at 1:03 PM, Vivek Vvk <wiwe...@gmail.com> wrote:
> Please suggest if we have any specific build process for rails app.
I'd call this more of a "deployment" than "build" tool, but it's most
definitely in widespread use:
http://capistranorb.com/
HTH!
--
Hassan Schroeder ------------------------ hassan.s...@gmail.com
http://about.me/hassanschroeder
twitter: @hassan
Consulting Availability : Silicon Valley or remote
--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/0be8a91b-7bb0-454a-ae85-c96449b72b93%40googlegroups.com.