Great to know! Thank you!
Yurui
On 25 Apr 2019, 8:33 PM +0800, Neville Dipale , wrote:
> To add here, sometimes builds for unrelated changes are caused by your
> branch being behind master. I've noticed that whenever I rebase my changes
> to latest master, I reliably only trigger the Rust jobs to
To add here, sometimes builds for unrelated changes are caused by your
branch being behind master. I've noticed that whenever I rebase my changes
to latest master, I reliably only trigger the Rust jobs to run.
Maybe that could also help non-Arrow commiters :)
On Thu, 25 Apr 2019 at 14:11, Wes McKi
If you are an Arrow committer you can restart builds in the Travis CI
UI, but otherwise the method that Antoine indicated is the best option
for non-committers
On Thu, Apr 25, 2019 at 4:51 AM Antoine Pitrou wrote:
>
>
> Hi,
>
> I often do a force-push of identical contents, with a different
> cha
Hi,
I often do a force-push of identical contents, with a different
changeset id:
$ git commit -a --amend && git push --force
Regards
Antoine.
Le 25/04/2019 à 11:39, Yurui Zhou a écrit :
> Hey guys:
>
> When submitting PR to master, I often run into Travis CI build failures that
> are unr
I am experiencing the same problem.
I find a post here:
https://stackoverflow.com/questions/17606874/trigger-a-travis-ci-rebuild-without-pushing-a-commit
However, most methods do not work for me. Maybe I do not have enough
permission.
So repoen the PR can be a good choice for me.
Best,
Liya Fan
Hey guys:
When submitting PR to master, I often run into Travis CI build failures that
are unrelated to my changes. I usually close and reopen the PR to re-trigger
the build. Just wondering is there any other way (like a button) that allow me
to re-trigger the falling builds without closing an
