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/06/21 19:26:00 UTC

[jira] [Commented] (YETUS-61) support for gerrit

    [ https://issues.apache.org/jira/browse/YETUS-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16058063#comment-16058063 ] 

Sean Busbey commented on YETUS-61:
----------------------------------

hurm. wonder why precommit didn't post here. I'll chase it down later.

Thanks for working on this! It would help me remove a bunch of cruft where I'm using Yetus on some internal systems.

bq. Basic case works. Trying to wonder which other feature from jira/github needs to be present for gerrit.

one thing I don't see present is target branch determining. IIRC, gerrit has this as an explicit part of the review request, which should be much more reliable than the guess-based-on-patch-name stuff we do in JIRA.

> support for gerrit
> ------------------
>
>                 Key: YETUS-61
>                 URL: https://issues.apache.org/jira/browse/YETUS-61
>             Project: Yetus
>          Issue Type: New Feature
>          Components: Test Patch
>            Reporter: Sean Busbey
>            Assignee: Suraj Acharya
>
> for projects that rely on gerrit for reviews and test-patch for the "verified" CI check, it would be nice if we could put review feedback on gerrit instead of in the issue tracker.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)