[
https://issues.apache.org/jira/browse/YETUS-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17222936#comment-17222936
]
Sean Busbey commented on YETUS-1059:
------------------------------------
maybe more complicated then is worth doing in this particular jira, but as
someone who works on a large project where precommit regularly takes 6-8 hours
to run what if we added a workflow for batching status updates?
* yetus launches as precommit for PRs as normal
* if status write fails, generate an artifact with the needed details. have
e.g. jenkins archive said artifact
* add a periodic maintenance job that can check the archived artifacts on a job
for these "I still need to update status" markers and then use a token it has
gotten to update various PR status
> Bring back github comments mode
> -------------------------------
>
> Key: YETUS-1059
> URL: https://issues.apache.org/jira/browse/YETUS-1059
> Project: Yetus
> Issue Type: Improvement
> Components: Precommit
> Affects Versions: 0.13.0
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Priority: Major
>
> Github insists that app tokens are only good for an hour which makes them
> useless for incredibly large projects or incredibly broken repositories. On
> systems that don't have a way to programmatically get a new token (looking at
> you, Jenkins), test-patch fails to write statuses.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
