You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@yetus.apache.org by "Sean Busbey (JIRA)" <ji...@apache.org> on 2017/05/16 15:59:04 UTC

[jira] [Updated] (YETUS-507) Add option to suppress output if patch detection fails

     [ https://issues.apache.org/jira/browse/YETUS-507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Busbey updated YETUS-507:
------------------------------
    Component/s: Test Patch

> Add option to suppress output if patch detection fails
> ------------------------------------------------------
>
>                 Key: YETUS-507
>                 URL: https://issues.apache.org/jira/browse/YETUS-507
>             Project: Yetus
>          Issue Type: Improvement
>          Components: Test Patch
>            Reporter: Mike Drob
>
> I'd like to be able to use Yetus with a JIRA workflow that doesn't have a Patch Available state. This means that I'll be looking at all attachment updates as they come in, some of which will be patches, but others will be screenshots, logs, etc.
> Instead of downloading the latest attachment, figuring out what it is, and then potentially triggering Yetus, I'd like to be able to delegate that to Yetus since I think it already has that logic (and would be doing patch detection anyway). Then, when an attachment fails patch detection, I'd like Yetus to fail silently instead of updating the JIRA with a -1 precommit check. There's no reason to post an update when somebody gives me a screenshot, and the -1 would likely confuse people more than it would help on the true patch apply failures.
> This should be a configurable option that is off by default.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)