> On Dec 22, 2020, at 7:05 PM, Jonathan Eagles <jeag...@gmail.com> wrote:
>
> Thanks for your reply. Commenting to github and possibly mirroring to JIRA
> would be fine.
>
> In this case the yetus report does not get posted to either jira or github.
> Instead I get a PR check status update that shows the success status of the
> jenkins build and a link back.
> PR reference: https://github.com/apache/tez/pull/85
>
> It sounds like something is not working with the github comment, but the
> build check. Those look like they have separate credentials being used as
> one is part of yetus and one is part of jenkins.
>
> Upgrading to 0.13.0 would require using the github app feature. I tried
> upgrading to 0.13.0 and using the built-in credentials from apache's
> ci-hadoop, still no comments, but also build check status stopped working.
> I will try running off of a fork adding some debugging information to the
> github comment feature as the output is silenced and no failures are
> printed even with --debugging on.
Looking at what is going on, it appears that Tez is way way way off-course,
even with the current stuff it is running.
Try something like this:
https://github.com/aw-was-here/tez/tree/y0130
Not really tested, but should push you closer to what you probably want/need.
It was tempting to just use a FROM of apache/yetus:0.13.0 and then plop in that
ancient version of protobuf to make the Docker build super fast. But giving you
a raw Dockerfile should help out if someone wants to see what is happening
under the hood.
