They all do the same things, the only difference what I see is a pricing and limitations for cloud-based jenkins/drone/travis (don't know is there a cloud-based TeamCity services). CloudBees based on Jenkins has 100 min/month for free projects while drone.io does not have monthly limitations for open source. But drone.io has 30-min compile-time limitation which they say can be removed. Travis.CI site says that there are no limitation for open source projects, but somewhere I saw that it has 1 hour limit to compile time.
For open-source project it's a good to have ability to avoid thinking about additional infrastructure for CI, its cost and maintenance. So in this case using cloud-based travis or drone can help devs to concentrate on software itself without spending their time and money to supporting internal CI build server. On Fri, 2014-06-13 at 12:24 -0700, Daniel Lo Nigro wrote: > Maybe drone could be used for > CI. https://github.com/drone/drone/ > > > What does Drone do that other more common CI systems like Jenkins and > TeamCity don't do? > > > On Fri, Jun 13, 2014 at 11:59 AM, Sergey Zhukov <[email protected]> wrote: > On Fri, 2014-06-13 at 09:12 -0700, Bob Summerwill wrote: > > > Maybe drone could be used for CI. > https://github.com/drone/drone/ > > Also for open-source project you can try travis.ci, but it has > one-hour > limit for running what can be critical for running mono tests > inside the > tizen emulator. > > > > > For Tizen at least I would like to get automated builds and > runs going > > within Windows Azure VMs which I will "sponsor" the costs of > runnin. > > Is there an existing automation infrastructure for this to > be added > > to? Thanks! > > > > > > > > > _______________________________________________ > Mono-devel-list mailing list > [email protected] > http://lists.ximian.com/mailman/listinfo/mono-devel-list > > > _______________________________________________ Mono-devel-list mailing list [email protected] http://lists.ximian.com/mailman/listinfo/mono-devel-list
