4 ms·
1. Atlassian Bamboo for polling my git repository for changes 2. Apache ANT for the build script 3. Then back out to a production/tarball git repo 4. Every l
by rajivtiru 13y ago
1. Atlassian Bamboo for polling my git repository for changes
2. Apache ANT for the build script
3. Then back out to a production/tarball git repo
4. Every load balanced server image has a cron job to poll the production git for changes
This way all I( or my team members) have to do is push to git.
Everything else is automated. All servers load balancing will keep themselves up to date.
- X4 13y agoThat's quite nice, but your weakness is that a single-point of failure can delay your deployment, without you noticing it early enough. Or do you have solution for that?
- rajivtiru 13y agoWe stage all changes on a 'develop' branch and run the same exact build process(thanks to bamboo) and deploy to the staging server. If QA passes, then we just merge the changes to master, push and deploy to production servers. Bamboo has a nice variety of test suites you can run too. I really like that git(via bitbucket) and bamboo notify hipchat of any build failures/updates so we can respond immediately if something serious actually goes wrong.