[jira] [Commented] (HBASE-24572) release scripts should try to use a keyid when refering to GPG keys.

["Hudson (Jira)" <ji...@apache.org>]

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

Hudson commented on HBASE-24572:
--------------------------------

Results for branch master
	[build #1801 on builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1801/]: (x) *{color:red}-1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general report|https://builds.apache.org/job/HBase%20Nightly/job/master/1801/General_20Nightly_20Build_20Report/]






(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) report|https://builds.apache.org/job/HBase%20Nightly/job/master/1801/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 report|https://builds.apache.org/job/HBase%20Nightly/job/master/1801/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(x) {color:red}-1 client integration test{color}
--Failed when running client tests on top of Hadoop 2. [see log for details|https://builds.apache.org/job/HBase%20Nightly/job/master/1801//artifact/output-integration/hadoop-2.log]. (note that this means we didn't run on Hadoop 3)


> release scripts should try to use a keyid when refering to GPG keys.
> --------------------------------------------------------------------
>
>                 Key: HBASE-24572
>                 URL: https://issues.apache.org/jira/browse/HBASE-24572
>             Project: HBase
>          Issue Type: Task
>          Components: build, community
>            Reporter: Nick Dimiduk
>            Assignee: Sean Busbey
>            Priority: Major
>             Fix For: 3.0.0-alpha-1
>
>
> Right now the template us substituting the release manager's email address in for the variable {{GPG_KEY}}. I think it doesn't hurt to make note of the email address, but what we really want here is the key's fingerprint, or some meaningly identifiable portion of it.



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