[
https://issues.apache.org/jira/browse/YETUS-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17530826#comment-17530826
]
Allen Wittenauer edited comment on YETUS-633 at 5/2/22 4:55 PM:
----------------------------------------------------------------
Basically, to extend Apache Yetus to integrate further with Github requires a
Github App. The only reasonable way to get a Github App working is to have a
running service that accepts OAuth and Webhook callbacks. At that point,
Apache Yetus is basically becoming its own CI system and would absolutely
require a top-to-bottom rewrite. With 0.13, precommit does a fairly reasonable
integration job with Github Status and Github Checks by leveraging off of the
permissions of the Github token that the CI system provides (assuming it is a
Github App proxied token) without taking that next jump.
was (Author: aw):
Basically, to extend Apache Yetus to integrate further with Github requires a
Github App. The only reasonable way to get a Github App working is to have a
running service that accepts OAuth and Webhook callbacks. At that point,
Apache Yetus is basically becoming its own CI system and would absolutely
require a top-to-bottom rewrite. With 0.13, precommit does a fairly reasonable
integration job with Github Status and Github Checks by leveraging off of the
permissions of the Github token that the CI system provides (assuming it is a
Github App token) without taking that next jump.
> GitHub Checks integration
> -------------------------
>
> Key: YETUS-633
> URL: https://issues.apache.org/jira/browse/YETUS-633
> Project: Yetus
> Issue Type: Wish
> Components: Precommit
> Reporter: Sean Busbey
> Priority: Major
>
> GitHub has launched a feature for putting CI feedback into its own tab:
> https://github.com/apache/yetus/pull/12/checks
> Would be nice. lots of open questions.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
