[
https://issues.apache.org/jira/browse/YETUS-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16012987#comment-16012987
]
Mike Drob commented on YETUS-507:
---------------------------------
Oh, that is fantastic! I was under the impression that we had still kept the
test-patch behavior of complaining as loud and as often as possible.
Feel free to close as a duplicate of whatever the appropriate issue is, then.
Thanks!
> 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)
