<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Mar 19, 2019 at 2:04 PM Tom Stellard <<a href="mailto:tstellar@redhat.com">tstellar@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 03/19/2019 10:24 AM, Eric Fiselier via llvm-dev wrote:<br>
> Hi All,<br>
> <br>
> Appveyor is a CI product for Windows. It's free for open source projects on Github.<br>
> Libc++ has been using it via the llvm-mirror organization on Github [1].<br>
> <br>
> Should we set Appveyor up for the official LLVM Github organization?<br>
> <br>
<br>
What exactly do you want to do?  Are you just looking to add a post-commit<br>
hook to trigger Appveyor builds?<br></blockquote><div><br></div><div>Authorizing the Appveyor Github App is one necessary step.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
-Tom<br>
<br>
> 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.<br>
> <br>
> /Eric<br>
> <br>
> [1] <a href="https://ci.appveyor.com/project/llvm-mirror/libcxx" rel="noreferrer" target="_blank">https://ci.appveyor.com/project/llvm-mirror/libcxx</a><br>
> <br>
> <br>
> <br>
> _______________________________________________<br>
> LLVM Developers mailing list<br>
> <a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a><br>
> <a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
> <br>
<br>
</blockquote></div></div>