[
https://issues.apache.org/jira/browse/PHOENIX-7446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17893741#comment-17893741
]
Nick Dimiduk commented on PHOENIX-7446:
---------------------------------------
In HBase we rely entirely on the gpg-agent being setup ahead of time. That is,
it is configured with a very long timeout and has already been unlocked for
signing. It's not a great solution, but it's working for us.
You may also be interested in HBASE-27312, MGPG-92.
> Document GPG passphrase handling in release process
> ---------------------------------------------------
>
> Key: PHOENIX-7446
> URL: https://issues.apache.org/jira/browse/PHOENIX-7446
> Project: Phoenix
> Issue Type: Task
> Reporter: Istvan Toth
> Priority: Major
>
> It seems like the maven GPG plugin is no longer able to ask for a passphrase,
> and it has also been disabled for the tar.gz signing in the release script.
> It seems like we need to somehow preset the passphrase before running the
> release script.
> It seems that this requires either modifying the gpg-agent cache times so
> that it's longer than the release process, or using the gpg-preset-passphrase
> tool.
> Figure this out and document on the release page on the website and/or the
> release script README.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
