Re: Another Travis networking issue :(

Yes. This is about PRs coming from forks. Currently GiltLab mirrors only the main repo to their own mirror. In order to get PRs from other forks working, they have to get commits from those other repos. Indeed it's different to use the public runners vs Kubernetes ones. For now Travis will remain

Re: Another Travis networking issue :(

Hey Jarek, AFAIK Gitlab implemented PR builds earlier this year, do they only trigger if the PR is coming from the same project? Also on another note, I wanted to point out that there are environment differences on Gitlab CI when CI runners run on Kubernetes vs when they run in VMs w/ plain old d

Re: Another Travis networking issue :(

Yep. Actions might be interesting indeed - especially when they introduce Self-Hosted Runners (this is coming next for Github Actions). Then we could do Github Actions + GKE runner :). That might be the best of both worlds. I will try it before I go for holidays. I expect though that it will be ha

Re: Another Travis networking issue :(

Or this: https://github.blog/2019-08-08-github-actions-now-supports-ci-cd/ (But GKE+Gitlab sounds fine to me) Sent from my iPhone > On 8 Aug 2019, at 11:44, Jarek Potiuk wrote: > > Indeed. > > I will try to get the automated builds on GitLabCI working from master > before my holidays so that

Re: Corrupted RAT .jar with builds

The fix is merged. Also the problem with Travis is resolved. You can now rebase your PRs on master. J. On Thu, Aug 8, 2019 at 12:48 PM Jarek Potiuk wrote: > Seems we have some other problem as well - corrupted JAR file downloaded > from Apache has been added to the CI docker file. The fix is al

Corrupted RAT .jar with builds

Seems we have some other problem as well - corrupted JAR file downloaded from Apache has been added to the CI docker file. The fix is also on it's way: https://github.com/apache/airflow/pull/5759 J. -- Jarek Potiuk Polidea | Principal Software Engineer M: +48 660 796

Re: Randomly failing cassandra to GCS test

The change is merged to master - please rebase on top of master to incorporate it. On Thu, Aug 8, 2019 at 11:50 AM Jarek Potiuk wrote: > On top of the Travis networking issues :( we had one flaky test added and > failing fairly often (Cassandra to GCS). The fix is on it's way > https://travis-ci

Randomly failing cassandra to GCS test

On top of the Travis networking issues :( we had one flaky test added and failing fairly often (Cassandra to GCS). The fix is on it's way https://travis-ci.org/apache/airflow/builds/569241255 . J. -- Jarek Potiuk Polidea | Principal Software Engineer M: +48 660 796 1

Re: Another Travis networking issue :(

Indeed. I will try to get the automated builds on GitLabCI working from master before my holidays so that it will automatically runs for quite a while (even if the Kubernetest/Kind tests are not yet working there) and hopefully we will be able to switch to GitLab + GKE soon. The only blocker there

Re: Another Travis networking issue :(

This is getting pretty annoying. On Thu, Aug 8, 2019 at 9:06 AM Jarek Potiuk wrote: > Her is the incident ... our builds are now failing on network timeouts > https://www.traviscistatus.com/incidents/bmh7gcb0v95t > > -- > > Jarek Potiuk > Polidea | Principal Software E

Another Travis networking issue :(

Her is the incident ... our builds are now failing on network timeouts https://www.traviscistatus.com/incidents/bmh7gcb0v95t -- Jarek Potiuk Polidea | Principal Software Engineer M: +48 660 796 129 <+48660796129> [image: Polidea]