[llvm-dev] How to trigger builds in Phabricator?

Jessica Paquette via llvm-dev llvm-dev at lists.llvm.org
Thu Nov 21 09:29:06 PST 2019

Unless things have changed lately and I missed something, you can just push the change and the bots will pick it up automatically. They will send you emails if it seems like anything is broken.

That being said, before pushing you should do some local tests (e.g. run the lit tests) as an initial sanity check.

If it breaks anything, the standard process is

1) Revert it with an explanation of why in the commit message. (E.g. “This broke this bot” with a link to the build log or a simple example.)
2) Fix the breakage
3) Recommit

- Jessica

> On Nov 21, 2019, at 12:23 AM, Ehud Katz via llvm-dev <llvm-dev at lists.llvm.org> wrote:
> Hi everyone,
> In the reviewing system, after a patch is approved, what should be the following step?
> I assume I'll have to make sure the patch hasn't broken anything, before pushing it, so I'll wan't to run a full build+tests, probably in a remote sterile environment (like a jenkins server).
> Do we have an integration system like this? Or should I just trust the build+tests on my machine?
> Regardless, I have seen in many reviews (in Phabricator) that Builds are triggered for them, in particular: "arc lint + arc unit" and "pre-merge checks" (which sounds like what I am searching for). What is their use and how do I trigger them?
> Thanks,
> Ehud.
> _______________________________________________
> 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/llvm-dev/attachments/20191121/470e9d21/attachment.html>

More information about the llvm-dev mailing list