You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@arrow.apache.org by Yurui Zhou <yu...@alibaba-inc.com> on 2019/04/25 09:39:00 UTC
Proper way to retrigger Travis CI builds
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 and reopening my PR?
Thanks
Yurui
Re: Proper way to retrigger Travis CI builds
Posted by Yurui Zhou <yu...@alibaba-inc.com>.
Great to know! Thank you!
Yurui
On 25 Apr 2019, 8:33 PM +0800, Neville Dipale <ne...@gmail.com>, 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 run.
> Maybe that could also help non-Arrow commiters :)
>
> On Thu, 25 Apr 2019 at 14:11, Wes McKinney <we...@gmail.com> wrote:
>
> > 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 <an...@python.org> wrote:
> > >
> > >
> > > 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 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 and
> > reopening my PR?
> > > >
> > > > Thanks
> > > > Yurui
> > > >
> >
Re: Proper way to retrigger Travis CI builds
Posted by Neville Dipale <ne...@gmail.com>.
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 McKinney <we...@gmail.com> wrote:
> 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 <an...@python.org> wrote:
> >
> >
> > 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 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 and
> reopening my PR?
> > >
> > > Thanks
> > > Yurui
> > >
>
Re: Proper way to retrigger Travis CI builds
Posted by Wes McKinney <we...@gmail.com>.
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 <an...@python.org> wrote:
>
>
> 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 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 and reopening my PR?
> >
> > Thanks
> > Yurui
> >
Re: Proper way to retrigger Travis CI builds
Posted by Antoine Pitrou <an...@python.org>.
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 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 and reopening my PR?
>
> Thanks
> Yurui
>
Re: Proper way to retrigger Travis CI builds
Posted by Fan Liya <li...@gmail.com>.
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
On Thu, Apr 25, 2019 at 5:39 PM Yurui Zhou <yu...@alibaba-inc.com>
wrote:
> 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 and
> reopening my PR?
>
> Thanks
> Yurui
>