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

Posted to issues@hbase.apache.org by "Nick Dimiduk (Jira)" <ji...@apache.org> on 2020/10/30 22:49:00 UTC

[jira] [Resolved] (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:all-tabpanel ]

Nick Dimiduk resolved HBASE-23888.
----------------------------------
    Resolution: Won't Fix

Per this [discuss thread|https://lists.apache.org/thread.html/r091e883c4075eb13a8df22a3298029fac66b97f1b6b0e2c8debc39e2%40%3Cdev.hbase.apache.org%3E], we have dropped support for receiving patches via Jenkins.

> 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)