Re:Show HN: UI improvements for Jenkins
by FreshCode on Tuesday October 01, 2013 @04:05AM
(#6474838)
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.
[ Parent
| on HN ]
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/...
* - I work for ThoughtWorks, but not associated with the Go team, and use Teamcity and Jenkins more than Go.
Re:Show HN: UI improvements for Jenkins
by shaggyfrog on Tuesday October 01, 2013 @11:33AM
(#6476821)
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.
is it free?