What tools do you use for Automated Builds / Automated Deployments? Why? [closed]

Answer 1

UppercuT uses NAnt to build and it is the insanely easy to use Build Framework.

Automated Builds as easy as (1) solution name, (2) source control path, (3) company name for most projects!

http://code.google.com/p/uppercut/

Some good explanations here: UppercuT

More information

---

UppercuT is a conventional automated build, which means you set up a config file and then you get a bunch of features for free. Arguably the most powerful feature is the ability to specify environment settings in ONE place and have them applied everywhere, including documentation when it builds the source.

Documentation available: https://github.com/chucknorris/uppercut/wiki

Features :

• Simple setup
• Simple upgrades
• Custom extension points (pre, post, and replace) for each step of the build process http://uppercut.pbworks.com/CustomizeUsingExtensionPoints
• Has documentation for integration w/Team City, CruiseControl.NET, and Jenkins (formerly Hudson) https://github.com/chucknorris/uppercut/tree/master/docs
• Works on Linux w/Mono
• Versioning DLLs based on build number and source control revisions (SVN, TFS, Git, HG)
• Compile activities - F5 or Ctrl + Shift + B
• Strong naming made as easy as true/false
• Code Testing and Analysis
  • Testing
    • NUnit
    • MbUnit v2
    • Gallio
    • xUnit
  • NCover
  • NDepend
  • Nitriq
  • Mono Migration Analyzer
• Obfuscation
• ILMerge
• Environment Templating and Building (ConfigBuilder, DocBuilder, SQLBuilder, DeploymentBuilder) https://github.com/chucknorris/uppercut/blob/master/docs/ConfigBuilder.doc?raw=true
• Packaging output to prepare for deployment
• Zips up output

Answer 2

The GNU Autotools definitely. The autoconf and automake are de-facto standard for unix systems.

Answer 3

TeamCity running NAnt scripts for building/packaging and PowerShell for deployment.

I've found that using NAnt, powered by TeamCity, instead of the native TeamCity runners allows us to have a much richer build process (eg. css minimiser, etc). It also means the full build/package process can be run on any developers PC instead of just the TeamCity servers making it much easier to customise and debug problems in the build process.

Answer 4

make and bash on linux

make and cmd on windows

Answer 5

Visual Build Pro

Answer 6

We use TeamCity, from JetBrains. They also make Resharper And IntelliJ.

We use it for building our .Net applications, and it has been quite easy to set up, connect to TFS, and run additional tools from. It is very polished, and actually kinda reminds me of this site. Found it much nicer than CruiseControl, and for our team size it is free. If you need lots of different builds, more per-user builds, and so on then it costs a bit (but still quite reasonable).