Poll: What do you use for deploying code? • Hacker News Board

Re: Poll: What do you use for deploying code?

#61

Post by misiti3780 » Wed, Jun 12, 2013, 2:04 PM UTC

leetrout wrote: post #41

misiti3780 wrote: post #30

Earlier quoted context omitted.

can you give more info on how you do this ?

Take a look at http://hynek.me/articles/python-app-deployment-with-native-p...

thanks

Re: Poll: What do you use for deploying code?

#62

Post by misiti3780 » Wed, Jun 12, 2013, 2:06 PM UTC

gecko wrote: post #37

misiti3780 wrote: post #29

Earlier quoted context omitted.

also - can anyone comment on what is the closet thing to chef written in the best language every, python :)

SaltStack ( http://saltstack.com/community.html ) and Ansible ( http://ansible.cc ) would be your two closest options. Of the two, I prefer Ansible for its simplicity and the fact that it can be extended in any language, but it's worth noting that that simplicity currently comes at a cost of power compared to Chef. (E.g., Chef has a concept of "ensure this service is present," and that works on all supported operatin…

thanks

Re: Poll: What do you use for deploying code?

#63

Post by abrudtkuhl » Wed, Jun 12, 2013, 4:32 PM UTC

joeyguerra wrote: post #15

Jenkins + Powershell in our Microsoft stack.

Would love more info on this setup.... looking to do the same in our shop

Re: Poll: What do you use for deploying code?

#64

Post by abrudtkuhl » Wed, Jun 12, 2013, 7:04 PM UTC

Is anyone using Octopus for .NET stack deployment? http://octopusdeploy.com/

Re: Poll: What do you use for deploying code?

#65

Post by rajivtiru » Thu, Jun 13, 2013, 12:36 AM UTC

X4 wrote: post #59

rajivtiru wrote: post #32

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.

That'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?

We 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.