You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@yetus.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2019/02/01 22:52:00 UTC

[jira] [Updated] (YETUS-788) expose patch analysis

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

Allen Wittenauer updated YETUS-788:
-----------------------------------
    Attachment: YETUS-788.00.patch

> expose patch analysis
> ---------------------
>
>                 Key: YETUS-788
>                 URL: https://issues.apache.org/jira/browse/YETUS-788
>             Project: Yetus
>          Issue Type: New Feature
>          Components: Test Patch
>    Affects Versions: 0.9.0
>            Reporter: Allen Wittenauer
>            Assignee: Allen Wittenauer
>            Priority: Major
>         Attachments: YETUS-788.00.patch
>
>
> Expose precommit's patch analysis so that decisions can be made based upon what a patch touches.  For example, if a change hits a certain set of directories or hits a certain module, some pre-work may be required prior to running test-patch.  
> Since Yetus already has the logic to do the hard work, this should just be a matter of exposing the results of that work.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)