Re: [RESULT][VOTE] Migrate to sponsored Travis account

Update: Implemented and deployed. On 02/08/2019 12:11, Jark Wu wrote: Wow. That's great! Thanks Chesnay. On Fri, 2 Aug 2019 at 17:50, Chesnay Schepler > wrote: I'm currently modifying the cibot to do this automatically; should be finished until Monday.

Re: [RESULT][VOTE] Migrate to sponsored Travis account

Wow. That's great! Thanks Chesnay. On Fri, 2 Aug 2019 at 17:50, Chesnay Schepler wrote: > I'm currently modifying the cibot to do this automatically; should be > finished until Monday. > > On 02/08/2019 07:41, Jark Wu wrote: > > Hi Chesnay, > > > > Can we assign Flink Committers the permission

Re: [RESULT][VOTE] Migrate to sponsored Travis account

I'm currently modifying the cibot to do this automatically; should be finished until Monday. On 02/08/2019 07:41, Jark Wu wrote: Hi Chesnay, Can we assign Flink Committers the permission of flink-ci/flink repo? Several times, when I pushed some new commits, the old build jobs are still in

Re: [RESULT][VOTE] Migrate to sponsored Travis account

Hi Chesnay, Can we assign Flink Committers the permission of flink-ci/flink repo? Several times, when I pushed some new commits, the old build jobs are still in pending and not canceled. Before we fix that, we can manually cancel some old jobs to save build resource. Best, Jark On Wed, 10 Jul

Re: [RESULT][VOTE] Migrate to sponsored Travis account

Your best bet would be to check the first commit in the PR and check the parent commit. To re-run things, you will have to rebase the PR on the latest master. On 10/07/2019 03:32, Kurt Young wrote: Thanks for all your efforts Chesnay, it indeed improves a lot for our develop experience. BTW,

Re: [RESULT][VOTE] Migrate to sponsored Travis account

Thanks for all your efforts Chesnay, it indeed improves a lot for our develop experience. BTW, do you know how to find the master branch information which the CI runs with? For example, like this one: https://travis-ci.com/flink-ci/flink/jobs/214542568 It shows pass with the commits, which

Re: [RESULT][VOTE] Migrate to sponsored Travis account

The kinks have been worked out; the bot is running again and pr builds are yet again no longer running on ASF resources. PRs are mirrored to: https://github.com/flink-ci/flink Bot source: https://github.com/flink-ci/ci-bot On 08/07/2019 17:14, Chesnay Schepler wrote: I have temporarily

Re: [RESULT][VOTE] Migrate to sponsored Travis account

I have temporarily re-enabled running PR builds on the ASF account; migrating to the Travis subscription caused some issues in the bot that I have to fix first. On 07/07/2019 23:01, Chesnay Schepler wrote: The vote has passed unanimously in favor of migrating to a separate Travis account. I

Re: [RESULT][VOTE] Migrate to sponsored Travis account

Yes we can do that; for the time being you can add an empty commit to re-trigger the CI. On 08/07/2019 03:49, Congxian Qiu wrote: As we used flink bot to trigger the CI test, could we add a command for flink bot to retrigger the CI(sometimes we may encounter some flaky tests) Best, Congxian

Re: [RESULT][VOTE] Migrate to sponsored Travis account

As we used flink bot to trigger the CI test, could we add a command for flink bot to retrigger the CI(sometimes we may encounter some flaky tests) Best, Congxian Chesnay Schepler 于2019年7月8日周一 上午5:01写道： > The vote has passed unanimously in favor of migrating to a separate > Travis account. > >

[RESULT][VOTE] Migrate to sponsored Travis account

The vote has passed unanimously in favor of migrating to a separate Travis account. I will now set things up such that no PullRequest is no longer run on the ASF servers. This is a major setup in reducing our usage of ASF resources. For the time being we'll use free Travis plan for flink-ci