<div dir="ltr">Hi David,<div>Please use the following issue to discuss on that:</div><div><a href="https://github.com/buildbot/buildbot/issues/3998">https://github.com/buildbot/buildbot/issues/3998</a><br></div><div><br></div><div>Pierre</div></div><br><div class="gmail_quote"><div dir="ltr">On Wed, Apr 18, 2018 at 11:10 PM David Alves <<a href="mailto:davidralves@gmail.com">davidralves@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi<br>
<br>
I've seen sporadic build issues when pushing a new rev of a <br>
GitHub pull request<br>
because buildbot pulls the merge ref and the merge ref is often <br>
not immediately updated.<br>
This causes the build triggered by the updated rev to actually <br>
use the merge ref<br>
corresponding to the previous rev, making the results of the <br>
build unreliable without<br>
re-checking that the correct code was actually tested.<br>
When contacted about this Github claimed merge refs are an <br>
undocumented feature and<br>
that they don't advise to use them.<br>
The alternative seems to be building from the head ref instead <br>
of the merge ref.<br>
IMO this makes sense. Would you be open to patch to fix this?<br>
<br>
Best<br>
--<br>
David Alves<br>
_______________________________________________<br>
users mailing list<br>
<a href="mailto:users@buildbot.net" target="_blank">users@buildbot.net</a><br>
<a href="https://lists.buildbot.net/mailman/listinfo/users" rel="noreferrer" target="_blank">https://lists.buildbot.net/mailman/listinfo/users</a><br>
</blockquote></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><p dir="ltr"><br></p>
</div></div>