[
https://issues.apache.org/jira/browse/HBASE-23888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17043937#comment-17043937
]
Sean Busbey commented on HBASE-23888:
-------------------------------------
We could experimentally verify if this still works properly but I'd rather just
not bother. Like the current setup doesn't even distinguish between "most
recent attachment" and "most recent patch" so it will happily fail the build if
you upload a patch and then a design off.
> 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)
