+1  “retest this please” is a very convenient command.
Jenkins has a plugin for this, wonder if travis-cli support this command.

Vinoth Chandar <vin...@apache.org> 于2020年5月28日周四 上午6:15写道:

> git commit --amend/git push --force has worked well for me. I am happy with
> it, personally - no extra commits, just changes the commit sha..
>
> I don't have strong opinions on this one. How easy is it to add "retest
> this please" or some automation like that..
>
> On Wed, May 27, 2020 at 2:49 PM Lamber Ken <lamber...@apache.org> wrote:
>
> > Hi Prashant Wason,
> >
> > "git push -f" command has no side effect. The purpose of this topic is to
> > reduce manual operations. The ci bot will help us to retry failure tests.
> >
> > For example, when use "retest thie please" command, the ci will retry
> > automatically
> > 1. Carbondata use "retest this please"
> >     https://github.com/apache/carbondata/pull/3387
> >
> > Thanks,
> > Lamber-Ken
> >
> > On 2020/05/27 21:24:57, Prashant Wason <pwa...@uber.com.INVALID> wrote:
> > > I have used force push (git push -f) to re-trigger Travis build. I
> don't
> > > know if force push has any side effect but it does save an extra
> commit.
> > >
> > > Thanks
> > > Prashant
> > >
> > >
> > > On Wed, May 27, 2020 at 11:11 AM Lamber Ken <lamber...@apache.org>
> > wrote:
> > >
> > > > Thanks Sivabalan
> > > >
> > > > For committers / pmcs, they can use these tools to trigger rebuilid
> > > > directly,
> > > > But for contributors, they can open the url, but the retrigger button
> > will
> > > > hidden.
> > > >
> > > > Best,
> > > > Lamber-Ken
> > > >
> > > >
> > > > On 2020/05/27 13:13:53, Sivabalan <n.siv...@gmail.com> wrote:
> > > > > Not sure if this is a common practice. But can't we trigger via
> > travis-ci
> > > > > directly? You can go here
> > > > > <
> > > >
> >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__travis-2Dci.org_github_apache_hudi_pull-5Frequests&d=DwIBaQ&c=r2dcLCtU9q6n0vrtnDw9vg&r=c89AU9T1AVhM4r2Xi3ctZA&m=xtI8Sm__cNsr2SNcNOd1TvHfk6eCk-zcl3mn1IagbGE&s=PTLkzOm-ocf96YucyzwNrhJ_yfQ3EB4zuNQSttiv6ow&e=
> > > > > or here
> > > > > <
> > > >
> >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__travis-2Dci.org_github_apache_hudi_builds&d=DwIBaQ&c=r2dcLCtU9q6n0vrtnDw9vg&r=c89AU9T1AVhM4r2Xi3ctZA&m=xtI8Sm__cNsr2SNcNOd1TvHfk6eCk-zcl3mn1IagbGE&s=wLjF5KLCkmXbjanjyE825M7qaSu2zf4qy2aUycf14ok&e=
> > > > > and there you can find an
> > > > > option to restart the build (right most column in every row) again
> if
> > > > need
> > > > > be. Wouldn't this suffice?
> > > > >
> > > > > On Wed, May 27, 2020 at 5:50 AM vino yang <yanghua1...@gmail.com>
> > wrote:
> > > > >
> > > > > > Hi Lamber-Ken,
> > > > > >
> > > > > > Thanks for opening this discussion.
> > > > > >
> > > > > > +1 to fix this issue.
> > > > > >
> > > > > > About the solution, can we consider to introduce a "CI Bot" just
> > like
> > > > > > Apache Flink has done?[1]
> > > > > >
> > > > > > Just a thought.
> > > > > >
> > > > > > Best,
> > > > > > Vino
> > > > > >
> > > > > > [1]:
> > > >
> >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_flink-2Dci_ci-2Dbot_&d=DwIBaQ&c=r2dcLCtU9q6n0vrtnDw9vg&r=c89AU9T1AVhM4r2Xi3ctZA&m=xtI8Sm__cNsr2SNcNOd1TvHfk6eCk-zcl3mn1IagbGE&s=Inll6__DlgwNzNDUKRbIhsW82R5SOdV45WMJQc4bS9o&e=
> > > > > >
> > > > > > Lamber Ken <lamber...@apache.org> 于2020年5月27日周三 下午2:08写道:
> > > > > >
> > > > > > > Dear community,
> > > > > > >
> > > > > > > Use case: A build fails due to an externality. The source is
> > actually
> > > > > > > correct. It would build OK and pass if simply re-run. Is there
> > some
> > > > way
> > > > > > to
> > > > > > > nudge Travis-CI to do another build, other than pushing a
> "dummy"
> > > > commit?
> > > > > > >
> > > > > > > The way I often used is `git commit --allow-empty -m 'trigger
> > > > rebuild'`,
> > > > > > > push a dummy commit, the travis will rebuild. Also noticed some
> > > > apache
> > > > > > > projects have supported this feature.
> > > > > > >
> > > > > > > For example:
> > > > > > > 1. Carbondata use "retest this please"
> > > > > > >
> > > >
> >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_carbondata_pull_3387&d=DwIBaQ&c=r2dcLCtU9q6n0vrtnDw9vg&r=c89AU9T1AVhM4r2Xi3ctZA&m=xtI8Sm__cNsr2SNcNOd1TvHfk6eCk-zcl3mn1IagbGE&s=vFZU-5zKAkGzQ9IgZEDjmjis0VRW4k2FvIPtMh6OfJY&e=
> > > > > > >
> > > > > > > 2. Bookkeeper use "run pr validation"
> > > > > > >
> > > >
> >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_bookkeeper_pull_2158&d=DwIBaQ&c=r2dcLCtU9q6n0vrtnDw9vg&r=c89AU9T1AVhM4r2Xi3ctZA&m=xtI8Sm__cNsr2SNcNOd1TvHfk6eCk-zcl3mn1IagbGE&s=bn4KGvHB9vXo7XsNhM4rcS_j1zK0m838kS4n0Fba0Bk&e=
> > > > > > >
> > > > > > > But, I can't find a effective solution from Github and Travis's
> > > > > > > documentation[1], any thoughts or opinions?
> > > > > > >
> > > > > > > Best,
> > > > > > > Lamber-Ken
> > > > > > >
> > > > > > > [1]
> > > >
> >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.travis-2Dci.com&d=DwIBaQ&c=r2dcLCtU9q6n0vrtnDw9vg&r=c89AU9T1AVhM4r2Xi3ctZA&m=xtI8Sm__cNsr2SNcNOd1TvHfk6eCk-zcl3mn1IagbGE&s=sOMap9ncNGc2hArVtrms1e4f7kLrLA0r9sfbFaFws0w&e=
> > > >
> > > >
> >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__support.github.com&d=DwIBaQ&c=r2dcLCtU9q6n0vrtnDw9vg&r=c89AU9T1AVhM4r2Xi3ctZA&m=xtI8Sm__cNsr2SNcNOd1TvHfk6eCk-zcl3mn1IagbGE&s=zQCZcD0hb-5FqLkW5W_jX0BF1ET48sQa1vpEZq7LXmU&e=
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Regards,
> > > > > -Sivabalan
> > > > >
> > > >
> > >
> >
>

Reply via email to