[jira] [Updated] (YETUS-272) add a way to flag/veto patches to code which jenkins doesn't test

["Steve Loughran (JIRA)" <ji...@apache.org>]

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

Steve Loughran updated YETUS-272:
---------------------------------
    Priority: Minor  (was: Major)

I can tell from that phrasing that you mean "it should be too hard for you, steve, to write it"...

> add a way to flag/veto patches to code which jenkins doesn't test
> -----------------------------------------------------------------
>
>                 Key: YETUS-272
>                 URL: https://issues.apache.org/jira/browse/YETUS-272
>             Project: Yetus
>          Issue Type: Improvement
>          Components: Test Patch
>            Reporter: Steve Loughran
>            Priority: Minor
>
> We have a recurrent problem in Hadoop where people submit patches related to s3, not realising that a yetus +1 doesn't mean that any of the s3 tests ran (they don't), and so there's risk/pressure that patches get committed without any actual tests.
> Could it be possible to provide a way to say "any patch under this path must be manually tested", and have patches vetoed if, say, they make any change to hadoop-tools/hadoop-aws



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)