<div dir="ltr"><div>Although I've not had any Github Action experience, and despite being one who has raised objections to other parts of adopting github features, this sounds like a sensible idea. It seems odd to me that we don't already have some form of CI for our releases, so anything that improves on that is great.</div><div><br></div><div>James<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 12 Nov 2019 at 00:34, David Blaikie via lldb-dev <<a href="mailto:lldb-dev@lists.llvm.org">lldb-dev@lists.llvm.org</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"><div dir="ltr">Not having given it deep thought/analysis, nor understanding much of the GIT infrastructure here, but: Sounds good to me, for whatever that's worth :)</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Nov 11, 2019 at 4:32 PM Tom Stellard via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</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">Hi,<br>
<br>
I would like to start using GitHub Actions[1] for CI testing on the release/*<br>
branches. As far as I know we don't have any buildbots listening to the<br>
release branches, and I think GitHub Actions are a good way for us to quickly<br>
bring-up some CI jobs there.<br>
<br>
My proposal is to start by adding two post-commit CI jobs to the release/9.x branch.<br>
One for building and testing (ninja checka-all) llvm/clang/lld on Linux,<br>
Windows, and Mac, and another for detecting ABI changes since the 9.0.0 release.<br>
<br>
I have already implemented these two CI jobs in my llvm-project fork on GitHub[2][3],<br>
but in order to get these running in the main repository, I would need to:<br>
<br>
1. Create a new repository in the LLVM organization called 'actions' for storing some custom<br>
builds steps for our CI jobs (see [4]).<br>
2. Commit yaml CI definitions to the .github/workflows directory in the release/9.x<br>
branch.<br>
<br>
In the future, I would also like to add buil and tests jobs for other sub-projects<br>
once I am able to get those working.<br>
<br>
In addition to being used for post-commit testing, having these CI definitions in the<br>
main tree will make it easier for me (or anyone) to do pre-commit testing for the<br>
release branch in a personal fork. It will also allow me to experiment with some new<br>
workflows to help make managing the releases much easier.<br>
<br>
I think this will be a good way to test Actions in a low traffic environment to<br>
see if they are something we would want to use for CI on the master branch.<br>
<br>
Given that we are close to the end of the 9.0.1 cycle, unless there are any<br>
strong objections, I would like to get this enabled by Mon Nov 18, to maximize its<br>
usefulness. Let me know what you think.<br>
<br>
Thanks,<br>
Tom<br>
<br>
[1] <a href="https://github.com/features/actions" rel="noreferrer" target="_blank">https://github.com/features/actions</a><br>
[2] <a href="https://github.com/tstellar/llvm-project/commit/952d80e8509ecc95797b2ddbf1af40abad2dcf4e/checks?check_suite_id=305765621" rel="noreferrer" target="_blank">https://github.com/tstellar/llvm-project/commit/952d80e8509ecc95797b2ddbf1af40abad2dcf4e/checks?check_suite_id=305765621</a><br>
[3] <a href="https://github.com/tstellar/llvm-project/commit/6d74f1b81632ef081dffa1e0c0434f47d4954423/checks?check_suite_id=303074176" rel="noreferrer" target="_blank">https://github.com/tstellar/llvm-project/commit/6d74f1b81632ef081dffa1e0c0434f47d4954423/checks?check_suite_id=303074176</a><br>
[4] <a href="https://github.com/tstellar/actions" rel="noreferrer" target="_blank">https://github.com/tstellar/actions</a><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>
</blockquote></div>
_______________________________________________<br>
lldb-dev mailing list<br>
<a href="mailto:lldb-dev@lists.llvm.org" target="_blank">lldb-dev@lists.llvm.org</a><br>
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev" rel="noreferrer" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev</a><br>
</blockquote></div>