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

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

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

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

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

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

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

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]

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

+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

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

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

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

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"

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

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

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

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

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

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

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

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,

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

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