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

Posted to issues@hbase.apache.org by "Sean Busbey (Jira)" <ji...@apache.org> on 2020/02/24 22:57:00 UTC

[jira] [Comment Edited] (HBASE-23888) PreCommit-HBASE-Build ignores the `ATTACHMENT_ID` provided by PreCommit-Admin

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

Sean Busbey edited comment on HBASE-23888 at 2/24/20 10:56 PM:
---------------------------------------------------------------

That's mostly correct afaik. Yetus should default to the most recent patch. If that patch correctly follows the naming convention for target branch then we should test in the correct branch.


was (Author: busbey):
That's mostly correct afaik. Yetus should default to the most recent patch. If that branch correctly follows the naming convention for target branch then we should test in the correct branch.

> PreCommit-HBASE-Build ignores the `ATTACHMENT_ID` provided by PreCommit-Admin
> -----------------------------------------------------------------------------
>
>                 Key: HBASE-23888
>                 URL: https://issues.apache.org/jira/browse/HBASE-23888
>             Project: HBase
>          Issue Type: Task
>          Components: build
>            Reporter: Nick Dimiduk
>            Priority: Major
>
> It appears that we've dropped the parameter {{ATTACHMENT_ID}} from our {{PreCommit-HBASE-Build}} job. (It may be the case that Yetus's {{test-patch}} doesn't support specifying what attachment id to test.) The result, I believe, is that when a Jira issue has patches attached for more than one branch, we only get precommit testing on the patch for master.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)