mxnet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Olivier <cjolivie...@gmail.com>
Subject Re: [VOTE] Disable Appveyor
Date Thu, 07 Dec 2017 23:43:44 GMT
Does Appveyor do anything that Jenkins isn't doing? Anything at all?

On Thu, Dec 7, 2017 at 3:41 PM, kellen sunderland <
kellen.sunderland@gmail.com> wrote:

> @Chris nope, AppVeyor has only ever supported Windows.
>
> I think some people are thinking of Travis CI, which is a pretty great
> managed CI that does support MacOS/Linux. I'd be in favour of setting up a
> Mac build there.  At a minimum we can at least start a new compiling task
> with clang in the new CI.
>
> On Dec 7, 2017 11:41 PM, "Indhu" <indhubharathi@gmail.com> wrote:
>
> > +1
> >
> > My build is waiting in queue for 13 hours now.
> >
> >
> > On Thu, Dec 7, 2017, 11:26 AM kellen sunderland <
> > kellen.sunderland@gmail.com>
> > wrote:
> >
> > > Background:  Appveyor is a free-to-use (for opensource) CI system that
> > > specializes in providing support for Windows environments.  Appveyor is
> > > currently running a very simple windows build for MXNet.  Specifically
> we
> > > are generating build files via cmake, and then building with Visual
> > Studio
> > > 14 with fairly standard build options.
> > >
> > > Problem: AppVeyor frequently slows down our release process and has
> been
> > > made redundant by the new CI system's windows builds.
> > >
> > > Action: Let's remove AppVeyor and rely on the new CI's windows build
> > > systems which has very similar functionality.
> > >
> > > Vote will close Monday Dec 11th and will rely on lazy consensus.
> > >
> > > -Kellen
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message