8 ms·

I opted to use TeamCity for all my CI exactly because of the UI. It's not perfect either, but I think it is vastly superior. Bigger install, though and relies o

I opted to use TeamCity for all my CI exactly because of the UI. It's not perfect either, but I think it is vastly superior. Bigger install, though and relies on a JVM.

borplk 13y ago
is it free?
- falsedan 13y ago
  The Professional license is free and gives 20 active build configurations & 3 simultaneous builds. I install extra instances if I need more.
manojlds 13y ago
You might also want to look at Go[1] from ThoughtWorks* - the UI and first class Pipeline support is it +ves. [1] - http://www.thoughtworks.com/products/go-continuous-delivery/compare http://www.thoughtworks.com/products/go-continuous-delivery/... * - I work for ThoughtWorks, but not associated with the Go team, and use Teamcity and Jenkins more than Go.
shaggyfrog 13y ago
Superior? Depends on what you're building. Using TeamCity to set up builds for iOS is a royal pain in the ass, and their OS X support in general is greatly lacking. I've had to create a whole ecosystem of shell scripts just to produce signed .ipa builds for QA -- which is kinda the point of purchasing a licence to a CI system to begin with.