Fwd: Prow will not able to check Travis context as Travis migrating off old status context API

[Michelle Au]

Patrick, could you help look into this?

---------- Forwarded message ---------
From: 'Sen Lu' via Kubernetes developer/contributor discussion <kuberne...@googlegroups.com>
Date: Thu, May 23, 2019 at 2:02 PM
Subject: Prow will not able to check Travis context as Travis migrating off old status context API
To: Kubernetes developer/contributor discussion <kuberne...@googlegroups.com>
Cc: Cole Wagner <co...@google.com>, <skuz...@redhat.com>

tl;dr

If you don't have Tide manages auto merge for your repo, or if you are not using Travis in your repo, you can stop reading now:

Slightly modified version from stevekuznetsov@'s notice:

FYI Travis seems to be finally migrating off of the old status context API and to the new checks api. This means that `tide` and `prow` in general cannot interact with it anymore. Specifically, the following repositories currently require the old status context in branch protection, which will mean that PRs where Travis reports using the Checks API have an un-run but required status from Travis, blocking merge:

`kubernetes/`
- `dashboard`
- `dns`
- `kompose`
- `kubectl`
- `repo-infra`
- `utils`
`kubernetes-client/`
- `python`
- `python-base`
`kubernetes-csi/`
- `csi-test`
- `drivers`
- `external-attacher`
- `external-provisioner`
- `external-snapshotter`
- `livenessprobe`
`kubernetes-incubator/`
- `apiserver-builder`
- `bootkube`
- `cluster-proportional-autoscaler`
- `external-storage`
- `kube-aws`
- `metrics-server`
`kubernetes-sigs/`
- `kube-batch`
- `node-feature-discovery` (edited)

All of the repos above must remove the requirement for Travis soon or they will block their merge queues. Furthermore, as Travis is now using Checks, we can no longer enforce that it is green before merging. If someone has the checks api required on their repo, `tide` will try to merge (as, for all it can see, everything is ready) but fail repeatedly as the check is not green

Those contexts can't be used anymore, so please migrate your jobs from Travis to Prow to avoid merge queue being stalled for your repos :-)

Thanks!

Best,

Sen
--

-------------------------------------------------

Sen Lu

Software Engineer

Google Kubernetes Engine - EngProd Team

--
You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-de...@googlegroups.com.
To post to this group, send email to kuberne...@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-dev.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/CA%2BSjBsRt_Xbt0m%2BrTbTqiEgWMgg45OO87sy7muki6t2qqs%2BxWA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Patrick Ohly]

Michelle Au <ms...@google.com> writes:
> Patrick, could you help look into this?

The Prow jobs are already a full replacement for testing in Travis. The
only reason why we keep Travis running is image publishing. That means
we can ignore Travis tests results - I just don't know where that needs
to be configured. I'll try to find out.

--
Best Regards

Patrick Ohly
Senior Software Engineer

Intel GmbH
Open Source Technology Center
Usenerstr. 5a Phone: +49-228-2493652
53129 Bonn
Germany

[Patrick Ohly]

"Patrick Ohly" <patric...@intel.com> writes:

> Michelle Au <ms...@google.com> writes:
>> Patrick, could you help look into this?
>
> The Prow jobs are already a full replacement for testing in Travis. The
> only reason why we keep Travis running is image publishing. That means
> we can ignore Travis tests results - I just don't know where that needs
> to be configured. I'll try to find out.

Should work for us again:
https://github.com/kubernetes/test-infra/pull/12768