[Mono-dev] Still seeking contractor to adding Tizen support to Mono
Brandon Perry
bperry.volatile at gmail.com
Fri Jun 13 21:46:37 UTC 2014
I can't recommend travis CI enough. We use it on the Metasploit project to
test pull requests for basic things automagically.
On Fri, Jun 13, 2014 at 4:44 PM, Sergey Zhukov <svg at ngs.ru> wrote:
> Anybody can use Travis.CI or drone.io as build system. They can run
> tests on different platforms. For example, here the post how to run
> tests on ARM platform using Travis.CI.
> http://www.tomaz.me/2013/12/02/running-travis-ci-tests-on-arm.html
>
> Also Travis.CI has built-in support for OSX and Ubuntu operating
> systems. So it's possible to write script, which will test mono across
> several tizen platforms the only bad thing could be a build time
> limitation.
>
>
> On Fri, 2014-06-13 at 14:27 -0700, Bob Summerwill wrote:
> >
> > Please could somebody confirm that there is no existing Mono project
> > automation?
> >
> > Outside of whatever Xamarin do for their own needs, I mean? Thanks!
> >
> >
> > Cheers,
> > Bob
> >
> >
> >
> >
> > On Fri, Jun 13, 2014 at 2:21 PM, Sergey Zhukov <svg at ngs.ru> wrote:
> > 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 <svg at ngs.ru>
> > 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
> > > Mono-devel-list at lists.ximian.com
> > >
> > http://lists.ximian.com/mailman/listinfo/mono-devel-list
> > >
> > >
> > >
> >
> >
> > _______________________________________________
> > Mono-devel-list mailing list
> > Mono-devel-list at lists.ximian.com
> > http://lists.ximian.com/mailman/listinfo/mono-devel-list
> >
> >
> >
> >
> > --
> > bob at summerwill.net
> >
> >
>
>
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>
--
http://volatile-minds.blogspot.com -- blog
http://www.volatileminds.net -- website
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/mono-devel-list/attachments/20140613/ae6da33f/attachment-0001.html>
More information about the Mono-devel-list
mailing list