Re: [DISSCUSS] Trigger a Travis-CI rebuild without pushing a commit

2020-06-08 Thread Vinoth Chandar 
Thanks Lamber-ken!  Please give me sometime to understand the PR and
review..

if anyone can jump on this in the meantime, please go ahead!

On Fri, Jun 5, 2020 at 3:33 PM Lamber Ken  wrote:

> Hi Vinoth,
>
> Based on the discussion above, I came up with an interesting idea that
> introduce a robot to build testing website automatically. If folks don't
> want to build staging site by themself, we can introduce a rebot which
> build testing website and push site automatically.
>
> I have already raised a lira for this:
> https://github.com/apache/hudi/pull/1706
> https://issues.apache.org/jira/browse/HUDI-998
>
> Thanks,
> Lamber-Ken
>
> On 2020/06/01 15:14:32, Vinoth Chandar  wrote:
> > Great!  I left some comment on the PR. around licensing and maintenance
> > overhead.
> >
> > On Sun, May 31, 2020 at 11:51 PM Lamber Ken 
> wrote:
> >
> > > Hi forks,
> > >
> > > Learned from travis and github actions api docs these days, I used my
> > > project as a demo[1],
> > > the demo pull request will always fail, please use "rerun tests"
> command,
> > > it will rerun tests automatically.
> > >
> > > if you are interested, try it.
> > >
> > > Best,
> > > Lamber-Ken
> > >
> > > [1] https://github.com/lamber-ken/hdocs/pull/36
> > >
> > >
> > > On 2020/05/27 06:08:05, Lamber Ken  wrote:
> > > > 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://github.com/apache/carbondata/pull/3387
> > > >
> > > > 2. Bookkeeper use "run pr validation"
> > > > https://github.com/apache/bookkeeper/pull/2158
> > > >
> > > > But, I can't find a effective solution from Github and Travis's
> > > documentation[1], any thoughts or opinions?
> > > >
> > > > Best,
> > > > Lamber-Ken
> > > >
> > > > [1] https://docs.travis-ci.comhttps://support.github.com
> > > >
> > >
> >
>

Re: [DISSCUSS] Trigger a Travis-CI rebuild without pushing a commit

2020-06-05 Thread Lamber Ken 
Hi Vinoth,

Based on the discussion above, I came up with an interesting idea that 
introduce a robot to build testing website automatically. If folks don't want 
to build staging site by themself, we can introduce a rebot which build testing 
website and push site automatically.

I have already raised a lira for this: 
https://github.com/apache/hudi/pull/1706
https://issues.apache.org/jira/browse/HUDI-998

Thanks,
Lamber-Ken

On 2020/06/01 15:14:32, Vinoth Chandar  wrote: 
> Great!  I left some comment on the PR. around licensing and maintenance
> overhead.
> 
> On Sun, May 31, 2020 at 11:51 PM Lamber Ken  wrote:
> 
> > Hi forks,
> >
> > Learned from travis and github actions api docs these days, I used my
> > project as a demo[1],
> > the demo pull request will always fail, please use "rerun tests" command,
> > it will rerun tests automatically.
> >
> > if you are interested, try it.
> >
> > Best,
> > Lamber-Ken
> >
> > [1] https://github.com/lamber-ken/hdocs/pull/36
> >
> >
> > On 2020/05/27 06:08:05, Lamber Ken  wrote:
> > > 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://github.com/apache/carbondata/pull/3387
> > >
> > > 2. Bookkeeper use "run pr validation"
> > > https://github.com/apache/bookkeeper/pull/2158
> > >
> > > But, I can't find a effective solution from Github and Travis's
> > documentation[1], any thoughts or opinions?
> > >
> > > Best,
> > > Lamber-Ken
> > >
> > > [1] https://docs.travis-ci.comhttps://support.github.com
> > >
> >
>

Re: [DISSCUSS] Trigger a Travis-CI rebuild without pushing a commit

2020-06-01 Thread Vinoth Chandar 
Great!  I left some comment on the PR. around licensing and maintenance
overhead.

On Sun, May 31, 2020 at 11:51 PM Lamber Ken  wrote:

> Hi forks,
>
> Learned from travis and github actions api docs these days, I used my
> project as a demo[1],
> the demo pull request will always fail, please use "rerun tests" command,
> it will rerun tests automatically.
>
> if you are interested, try it.
>
> Best,
> Lamber-Ken
>
> [1] https://github.com/lamber-ken/hdocs/pull/36
>
>
> On 2020/05/27 06:08:05, Lamber Ken  wrote:
> > 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://github.com/apache/carbondata/pull/3387
> >
> > 2. Bookkeeper use "run pr validation"
> > https://github.com/apache/bookkeeper/pull/2158
> >
> > But, I can't find a effective solution from Github and Travis's
> documentation[1], any thoughts or opinions?
> >
> > Best,
> > Lamber-Ken
> >
> > [1] https://docs.travis-ci.comhttps://support.github.com
> >
>

Re: [DISSCUSS] Trigger a Travis-CI rebuild without pushing a commit

2020-06-01 Thread Lamber Ken 
Hi forks,

Learned from travis and github actions api docs these days, I used my project 
as a demo[1],
the demo pull request will always fail, please use "rerun tests" command, it 
will rerun tests automatically.

if you are interested, try it.

Best,
Lamber-Ken

[1] https://github.com/lamber-ken/hdocs/pull/36


On 2020/05/27 06:08:05, Lamber Ken  wrote: 
> 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://github.com/apache/carbondata/pull/3387
> 
> 2. Bookkeeper use "run pr validation"
> https://github.com/apache/bookkeeper/pull/2158
> 
> But, I can't find a effective solution from Github and Travis's 
> documentation[1], any thoughts or opinions?
> 
> Best,
> Lamber-Ken
> 
> [1] https://docs.travis-ci.comhttps://support.github.com
>

Re: [DISSCUSS] Trigger a Travis-CI rebuild without pushing a commit

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

Vinoth Chandar  于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  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  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 
> > 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  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=DwIBaQ=r2dcLCtU9q6n0vrtnDw9vg=c89AU9T1AVhM4r2Xi3ctZA=xtI8Sm__cNsr2SNcNOd1TvHfk6eCk-zcl3mn1IagbGE=PTLkzOm-ocf96YucyzwNrhJ_yfQ3EB4zuNQSttiv6ow=
> > > > > or here
> > > > > <
> > > >
> >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__travis-2Dci.org_github_apache_hudi_builds=DwIBaQ=r2dcLCtU9q6n0vrtnDw9vg=c89AU9T1AVhM4r2Xi3ctZA=xtI8Sm__cNsr2SNcNOd1TvHfk6eCk-zcl3mn1IagbGE=wLjF5KLCkmXbjanjyE825M7qaSu2zf4qy2aUycf14ok=
> > > > > 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 
> > 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_=DwIBaQ=r2dcLCtU9q6n0vrtnDw9vg=c89AU9T1AVhM4r2Xi3ctZA=xtI8Sm__cNsr2SNcNOd1TvHfk6eCk-zcl3mn1IagbGE=Inll6__DlgwNzNDUKRbIhsW82R5SOdV45WMJQc4bS9o=
> > > > > >
> > > > > > Lamber Ken  于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=DwIBaQ=r2dcLCtU9q6n0vrtnDw9vg=c89AU9T1AVhM4r2Xi3ctZA=xtI8Sm__cNsr2SNcNOd1TvHfk6eCk-zcl3mn1IagbGE=vFZU-5zKAkGzQ9IgZEDjmjis0VRW4k2FvIPtMh6OfJY=
> > > > > > >
> > > > > > > 2. Bookkeeper use "run pr validation"
> > > > > > >
> > > >
> >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_bookkeeper_pull_2158=DwIBaQ=r2dcLCtU9q6n0vrtnDw9vg=c89AU9T1AVhM4r2Xi3ctZA=xtI8Sm__cNsr2SNcNOd1TvHfk6eCk-zcl3mn1IagbGE=bn4KGvHB9vXo7XsNhM4rcS_j1zK0m838kS4n0Fba0Bk=
> > > > > > >
> > > > > > > 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=DwIBaQ=r2dcLCtU9q6n0vrtnDw9vg=c89AU9T1AVhM4r2Xi3ctZA=xtI8Sm__cNsr2SNcNOd1TvHfk6eCk-zcl3mn1IagbGE=sOMap9ncNGc2hArVtrms1e4f7kLrLA0r9sfbFaFws0w=
> > > >
> > > >
> >
>

Re: [DISSCUSS] Trigger a Travis-CI rebuild without pushing a commit

2020-05-27 Thread Vinoth Chandar 
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  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  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 
> 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  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=DwIBaQ=r2dcLCtU9q6n0vrtnDw9vg=c89AU9T1AVhM4r2Xi3ctZA=xtI8Sm__cNsr2SNcNOd1TvHfk6eCk-zcl3mn1IagbGE=PTLkzOm-ocf96YucyzwNrhJ_yfQ3EB4zuNQSttiv6ow=
> > > > or here
> > > > <
> > >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__travis-2Dci.org_github_apache_hudi_builds=DwIBaQ=r2dcLCtU9q6n0vrtnDw9vg=c89AU9T1AVhM4r2Xi3ctZA=xtI8Sm__cNsr2SNcNOd1TvHfk6eCk-zcl3mn1IagbGE=wLjF5KLCkmXbjanjyE825M7qaSu2zf4qy2aUycf14ok=
> > > > 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 
> 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_=DwIBaQ=r2dcLCtU9q6n0vrtnDw9vg=c89AU9T1AVhM4r2Xi3ctZA=xtI8Sm__cNsr2SNcNOd1TvHfk6eCk-zcl3mn1IagbGE=Inll6__DlgwNzNDUKRbIhsW82R5SOdV45WMJQc4bS9o=
> > > > >
> > > > > Lamber Ken  于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=DwIBaQ=r2dcLCtU9q6n0vrtnDw9vg=c89AU9T1AVhM4r2Xi3ctZA=xtI8Sm__cNsr2SNcNOd1TvHfk6eCk-zcl3mn1IagbGE=vFZU-5zKAkGzQ9IgZEDjmjis0VRW4k2FvIPtMh6OfJY=
> > > > > >
> > > > > > 2. Bookkeeper use "run pr validation"
> > > > > >
> > >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_bookkeeper_pull_2158=DwIBaQ=r2dcLCtU9q6n0vrtnDw9vg=c89AU9T1AVhM4r2Xi3ctZA=xtI8Sm__cNsr2SNcNOd1TvHfk6eCk-zcl3mn1IagbGE=bn4KGvHB9vXo7XsNhM4rcS_j1zK0m838kS4n0Fba0Bk=
> > > > > >
> > > > > > 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=DwIBaQ=r2dcLCtU9q6n0vrtnDw9vg=c89AU9T1AVhM4r2Xi3ctZA=xtI8Sm__cNsr2SNcNOd1TvHfk6eCk-zcl3mn1IagbGE=sOMap9ncNGc2hArVtrms1e4f7kLrLA0r9sfbFaFws0w=
> > >
> > >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__support.github.com=DwIBaQ=r2dcLCtU9q6n0vrtnDw9vg=c89AU9T1AVhM4r2Xi3ctZA=xtI8Sm__cNsr2SNcNOd1TvHfk6eCk-zcl3mn1IagbGE=zQCZcD0hb-5FqLkW5W_jX0BF1ET48sQa1vpEZq7LXmU=
> > > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Regards,
> > > > -Sivabalan
> > > >
> > >
> >
>

Re: [DISSCUSS] Trigger a Travis-CI rebuild without pushing a commit

2020-05-27 Thread Lamber Ken 
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  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  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  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=DwIBaQ=r2dcLCtU9q6n0vrtnDw9vg=c89AU9T1AVhM4r2Xi3ctZA=xtI8Sm__cNsr2SNcNOd1TvHfk6eCk-zcl3mn1IagbGE=PTLkzOm-ocf96YucyzwNrhJ_yfQ3EB4zuNQSttiv6ow=
> > > or here
> > > <
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__travis-2Dci.org_github_apache_hudi_builds=DwIBaQ=r2dcLCtU9q6n0vrtnDw9vg=c89AU9T1AVhM4r2Xi3ctZA=xtI8Sm__cNsr2SNcNOd1TvHfk6eCk-zcl3mn1IagbGE=wLjF5KLCkmXbjanjyE825M7qaSu2zf4qy2aUycf14ok=
> > > 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  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_=DwIBaQ=r2dcLCtU9q6n0vrtnDw9vg=c89AU9T1AVhM4r2Xi3ctZA=xtI8Sm__cNsr2SNcNOd1TvHfk6eCk-zcl3mn1IagbGE=Inll6__DlgwNzNDUKRbIhsW82R5SOdV45WMJQc4bS9o=
> > > >
> > > > Lamber Ken  于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=DwIBaQ=r2dcLCtU9q6n0vrtnDw9vg=c89AU9T1AVhM4r2Xi3ctZA=xtI8Sm__cNsr2SNcNOd1TvHfk6eCk-zcl3mn1IagbGE=vFZU-5zKAkGzQ9IgZEDjmjis0VRW4k2FvIPtMh6OfJY=
> > > > >
> > > > > 2. Bookkeeper use "run pr validation"
> > > > >
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_bookkeeper_pull_2158=DwIBaQ=r2dcLCtU9q6n0vrtnDw9vg=c89AU9T1AVhM4r2Xi3ctZA=xtI8Sm__cNsr2SNcNOd1TvHfk6eCk-zcl3mn1IagbGE=bn4KGvHB9vXo7XsNhM4rcS_j1zK0m838kS4n0Fba0Bk=
> > > > >
> > > > > 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=DwIBaQ=r2dcLCtU9q6n0vrtnDw9vg=c89AU9T1AVhM4r2Xi3ctZA=xtI8Sm__cNsr2SNcNOd1TvHfk6eCk-zcl3mn1IagbGE=sOMap9ncNGc2hArVtrms1e4f7kLrLA0r9sfbFaFws0w=
> >
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__support.github.com=DwIBaQ=r2dcLCtU9q6n0vrtnDw9vg=c89AU9T1AVhM4r2Xi3ctZA=xtI8Sm__cNsr2SNcNOd1TvHfk6eCk-zcl3mn1IagbGE=zQCZcD0hb-5FqLkW5W_jX0BF1ET48sQa1vpEZq7LXmU=
> > > > >
> > > >
> > >
> > >
> > > --
> > > Regards,
> > > -Sivabalan
> > >
> >
>

Re: [DISSCUSS] Trigger a Travis-CI rebuild without pushing a commit

2020-05-27 Thread Prashant Wason 
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  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  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=DwIBaQ=r2dcLCtU9q6n0vrtnDw9vg=c89AU9T1AVhM4r2Xi3ctZA=xtI8Sm__cNsr2SNcNOd1TvHfk6eCk-zcl3mn1IagbGE=PTLkzOm-ocf96YucyzwNrhJ_yfQ3EB4zuNQSttiv6ow=
> > or here
> > <
> https://urldefense.proofpoint.com/v2/url?u=https-3A__travis-2Dci.org_github_apache_hudi_builds=DwIBaQ=r2dcLCtU9q6n0vrtnDw9vg=c89AU9T1AVhM4r2Xi3ctZA=xtI8Sm__cNsr2SNcNOd1TvHfk6eCk-zcl3mn1IagbGE=wLjF5KLCkmXbjanjyE825M7qaSu2zf4qy2aUycf14ok=
> > 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  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_=DwIBaQ=r2dcLCtU9q6n0vrtnDw9vg=c89AU9T1AVhM4r2Xi3ctZA=xtI8Sm__cNsr2SNcNOd1TvHfk6eCk-zcl3mn1IagbGE=Inll6__DlgwNzNDUKRbIhsW82R5SOdV45WMJQc4bS9o=
> > >
> > > Lamber Ken  于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=DwIBaQ=r2dcLCtU9q6n0vrtnDw9vg=c89AU9T1AVhM4r2Xi3ctZA=xtI8Sm__cNsr2SNcNOd1TvHfk6eCk-zcl3mn1IagbGE=vFZU-5zKAkGzQ9IgZEDjmjis0VRW4k2FvIPtMh6OfJY=
> > > >
> > > > 2. Bookkeeper use "run pr validation"
> > > >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_bookkeeper_pull_2158=DwIBaQ=r2dcLCtU9q6n0vrtnDw9vg=c89AU9T1AVhM4r2Xi3ctZA=xtI8Sm__cNsr2SNcNOd1TvHfk6eCk-zcl3mn1IagbGE=bn4KGvHB9vXo7XsNhM4rcS_j1zK0m838kS4n0Fba0Bk=
> > > >
> > > > 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=DwIBaQ=r2dcLCtU9q6n0vrtnDw9vg=c89AU9T1AVhM4r2Xi3ctZA=xtI8Sm__cNsr2SNcNOd1TvHfk6eCk-zcl3mn1IagbGE=sOMap9ncNGc2hArVtrms1e4f7kLrLA0r9sfbFaFws0w=
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__support.github.com=DwIBaQ=r2dcLCtU9q6n0vrtnDw9vg=c89AU9T1AVhM4r2Xi3ctZA=xtI8Sm__cNsr2SNcNOd1TvHfk6eCk-zcl3mn1IagbGE=zQCZcD0hb-5FqLkW5W_jX0BF1ET48sQa1vpEZq7LXmU=
> > > >
> > >
> >
> >
> > --
> > Regards,
> > -Sivabalan
> >
>

Re: [DISSCUSS] Trigger a Travis-CI rebuild without pushing a commit

2020-05-27 Thread Lamber Ken 
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  wrote: 
> Not sure if this is a common practice. But can't we trigger via travis-ci
> directly? You can go here
>  or here
>  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  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://github.com/flink-ci/ci-bot/
> >
> > Lamber Ken  于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://github.com/apache/carbondata/pull/3387
> > >
> > > 2. Bookkeeper use "run pr validation"
> > > https://github.com/apache/bookkeeper/pull/2158
> > >
> > > But, I can't find a effective solution from Github and Travis's
> > > documentation[1], any thoughts or opinions?
> > >
> > > Best,
> > > Lamber-Ken
> > >
> > > [1] https://docs.travis-ci.comhttps://support.github.com
> > >
> >
> 
> 
> -- 
> Regards,
> -Sivabalan
>

Re: [DISSCUSS] Trigger a Travis-CI rebuild without pushing a commit

2020-05-27 Thread Sivabalan 
Not sure if this is a common practice. But can't we trigger via travis-ci
directly? You can go here
 or here
 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  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://github.com/flink-ci/ci-bot/
>
> Lamber Ken  于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://github.com/apache/carbondata/pull/3387
> >
> > 2. Bookkeeper use "run pr validation"
> > https://github.com/apache/bookkeeper/pull/2158
> >
> > But, I can't find a effective solution from Github and Travis's
> > documentation[1], any thoughts or opinions?
> >
> > Best,
> > Lamber-Ken
> >
> > [1] https://docs.travis-ci.comhttps://support.github.com
> >
>


-- 
Regards,
-Sivabalan

Re: [DISSCUSS] Trigger a Travis-CI rebuild without pushing a commit

2020-05-27 Thread vino yang 
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://github.com/flink-ci/ci-bot/

Lamber Ken  于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://github.com/apache/carbondata/pull/3387
>
> 2. Bookkeeper use "run pr validation"
> https://github.com/apache/bookkeeper/pull/2158
>
> But, I can't find a effective solution from Github and Travis's
> documentation[1], any thoughts or opinions?
>
> Best,
> Lamber-Ken
>
> [1] https://docs.travis-ci.comhttps://support.github.com
>

[DISSCUSS] Trigger a Travis-CI rebuild without pushing a commit

2020-05-27 Thread Lamber Ken 
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://github.com/apache/carbondata/pull/3387

2. Bookkeeper use "run pr validation"
https://github.com/apache/bookkeeper/pull/2158

But, I can't find a effective solution from Github and Travis's 
documentation[1], any thoughts or opinions?

Best,
Lamber-Ken

[1] https://docs.travis-ci.comhttps://support.github.com