[
https://issues.apache.org/jira/browse/YETUS-742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer updated YETUS-742:
-----------------------------------
Fix Version/s: (was: 0.10.0)
> rework external communications
> ------------------------------
>
> Key: YETUS-742
> URL: https://issues.apache.org/jira/browse/YETUS-742
> Project: Yetus
> Issue Type: Improvement
> Components: Precommit
> Reporter: Allen Wittenauer
> Priority: Major
>
> There are a few inter-related things that should be tune-ables:
> - If a CI system has the ability to update the build status on a bug system
> (eg github), then it may be undesirable for Yetus to directly comment.
> - When multiple bug systems are configured, it should be possible to update
> either all of them or some of them or just one of them. Today, a PR that
> references a JIRA issue does not update that issue.
> - if HTML reporting is enabled, it'd be great to be able to just comment with
> a +/- 1 and a link to the HTML or, if there is a status field to supply a
> link, just use that (e.g., https://developer.github.com/v3/repos/statuses) .
> - Bonus points: use something like mustache for templating the actual content
> that gets posted.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
