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 o

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 pend

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 2

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, d

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 rebased

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-enabl

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 (i

Re: [VOTE] Migrate to sponsored Travis account

I have a prototype ready and will now commence a real world test. I will point it apache/flink and mirror it into a ververica controlled repo to start Travis runs. Once the run is finished the bot will comment on the PR with the results. This runs in addition to our existing CI. On 04/07/2019

Re: [VOTE] Migrate to sponsored Travis account

+1 for the migration Best, JingsongLee -- From:Jark Wu Send Time:2019年7月5日(星期五) 10:35 To:dev Cc:private ; Bowen Li Subject:Re: [VOTE] Migrate to sponsored Travis account +1 for the migration and great thanks to Chesnay and

Re: [VOTE] Migrate to sponsored Travis account

Sent: Friday, July 5, 2019 10:34 To: dev Cc: priv...@flink.apache.org; Bowen Li Subject: Re: [VOTE] Migrate to sponsored Travis account +1 for the migration and great thanks to Chesnay and Bowen for pushing this! Cheers, Jark On Fri, 5 Jul 2019 at 09:34, Congxian Qiu wrote: > +1 for

Re: [VOTE] Migrate to sponsored Travis account

+1 for the migration and great thanks to Chesnay and Bowen for pushing this! Cheers, Jark On Fri, 5 Jul 2019 at 09:34, Congxian Qiu wrote: > +1 for the migration. > > Best, > Congxian > > > Hequn Cheng 于2019年7月4日周四 下午9:42写道： > > > +1. > > > > And thanks a lot to Chesnay for pushing this. > > >

Re: [VOTE] Migrate to sponsored Travis account

+1 for the migration. Best, Congxian Hequn Cheng 于2019年7月4日周四 下午9:42写道： > +1. > > And thanks a lot to Chesnay for pushing this. > > Best, Hequn > > On Thu, Jul 4, 2019 at 8:07 PM Chesnay Schepler > wrote: > > > Note that the Flinkbot approach isn't that trivial either; we can't > > _just_ tri

Re: [VOTE] Migrate to sponsored Travis account

+1 on approval of the migration to our own Travis account. The foreseeable benefits of the whole community's productivity and iteration speed would be significant! I think using Flinkbot or Travis REST API would be an implementation details. Once we determine the overall direction, details can be

Re: [VOTE] Migrate to sponsored Travis account

+1. And thanks a lot to Chesnay for pushing this. Best, Hequn On Thu, Jul 4, 2019 at 8:07 PM Chesnay Schepler wrote: > Note that the Flinkbot approach isn't that trivial either; we can't > _just_ trigger builds for a branch in the apache repo, but would first > have to clone the branch/pr into

Re: [VOTE] Migrate to sponsored Travis account

Note that the Flinkbot approach isn't that trivial either; we can't _just_ trigger builds for a branch in the apache repo, but would first have to clone the branch/pr into a separate repository (that is owned by the github account that the travis account would be tied to). One roadblock after

Re: [VOTE] Migrate to sponsored Travis account

nd thanks for Chesnay' work on this. > > > > > > Best, > > > Zhijiang > > > > > > -- > > > From:Haibo Sun > > > Send Time:2019年7月4日(星期四) 18:21 > > > To:dev

Re: [VOTE] Migrate to sponsored Travis account

rk on this. > > > > Best, > > Zhijiang > > > > -- > > From:Haibo Sun > > Send Time:2019年7月4日(星期四) 18:21 > > To:dev > > Cc:priv...@flink.apache.org > > Subject:Re:Re: [VOTE] Migrate to sponsored Travis account > > > > +1. Thank Che

Re: [VOTE] Migrate to sponsored Travis account

> Send Time:2019年7月4日(星期四) 18:21 > To:dev > Cc:priv...@flink.apache.org > Subject:Re:Re: [VOTE] Migrate to sponsored Travis account > > +1. Thank Chesnay for pushing this forward. > > Best, > Haibo > > > At 2019-07-04 17:58:28, "Kurt Young"

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

+1 and thanks for Chesnay' work on this. Best, Zhijiang -- From:Haibo Sun Send Time:2019年7月4日(星期四) 18:21 To:dev Cc:priv...@flink.apache.org Subject:Re:Re: [VOTE] Migrate to sponsored Travis account +1. Thank Chesnay for pu

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

+1. Thank Chesnay for pushing this forward. Best, Haibo At 2019-07-04 17:58:28, "Kurt Young" wrote: >+1 and great thanks Chesnay for pushing this. > >Best, >Kurt > > >On Thu, Jul 4, 2019 at 5:44 PM Aljoscha Krettek wrote: > >> +1 >> >> Aljoscha >> >> > On 4. Jul 2019, at 11:09, Stephan Ewen w

Re: [VOTE] Migrate to sponsored Travis account

Small update with mostly bad news: INFRA doesn't know whether it is possible, and referred my to Travis support. They did point out that it could be problematic in regards to read/write permissions for the repository. From my own findings /so far/ with a test repo/organization, it does not a

Re: [VOTE] Migrate to sponsored Travis account

+1 and great thanks Chesnay for pushing this. Best, Kurt On Thu, Jul 4, 2019 at 5:44 PM Aljoscha Krettek wrote: > +1 > > Aljoscha > > > On 4. Jul 2019, at 11:09, Stephan Ewen wrote: > > > > +1 to move to a private Travis account. > > > > I can confirm that Ververica will sponsor a Travis CI p

Re: [VOTE] Migrate to sponsored Travis account

+1 Aljoscha > On 4. Jul 2019, at 11:09, Stephan Ewen wrote: > > +1 to move to a private Travis account. > > I can confirm that Ververica will sponsor a Travis CI plan that is > equivalent or a bit higher than the previous ASF quota (10 concurrent build > queues) > > Best, > Stephan > > On Th

Re: [VOTE] Migrate to sponsored Travis account

+1 to move to a private Travis account. I can confirm that Ververica will sponsor a Travis CI plan that is equivalent or a bit higher than the previous ASF quota (10 concurrent build queues) Best, Stephan On Thu, Jul 4, 2019 at 10:46 AM Chesnay Schepler wrote: > I've raised a JIRA >

[VOTE] Migrate to sponsored Travis account

I've raised a JIRA with INFRA to inquire whether it would be possible to switch to a different Travis account, and if so what steps would need to be taken. We need a proper confirmation from INFRA since we are not in full control of the flink r