[libcxx-dev] [llvm-dev] Appveyor for the LLVM Github Org

[Eric Fiselier via libcxx-dev]

On Tue, Mar 19, 2019 at 1:51 PM Roman Lebedev <lebedev.ri at gmail.com> wrote:

> On Tue, Mar 19, 2019 at 8:24 PM Eric Fiselier via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
> >
> > Hi All,
> >
> > Appveyor is a CI product for Windows. It's free for open source projects
> on Github.
> > Libc++ has been using it via the llvm-mirror organization on Github [1].
> >
> > Should we set Appveyor up for the official LLVM Github organization?
> >
> > The motivation for testing libc++ on Windows using Appveyor over
> Buildbot is that
> > Appveyor allows for a faster development cycle. CI configuration changes
> are
> > frequent at this stage of libc++ Windows support.
> > With buildbot these changes take a week to propagate.
>
> How would that work for LLVM?
> libc++ / libcxx are rather small projects so Appveyor works well for them.
> But LLVM as a whole is *huge*.
> It takes ~50 minutes (1 hour let's say) to build it for me with 8 cores.
> Appveyor builds are 2-4 cores, and severely ram-limited.
> So it would take 4..2 hours at best to build, and then there's tests.
> It doesn't sound all that promising?
>
> (also, only a single build at a time)
>

Appveyor may not be suitable for all cases. It may be too slow to use for
full LLVM builds.
Setting it up for the monorepo may be infeasible.

I raised the question in hopes of making libc++'s "unofficial" Appveyor
setup more official.



>
> > /Eric
> Roman.
>
> > [1] https://ci.appveyor.com/project/llvm-mirror/libcxx
> >
> > _______________________________________________
> > LLVM Developers mailing list
> > llvm-dev at lists.llvm.org
> > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/libcxx-dev/attachments/20190319/f367a6c0/attachment.html>