[ 
https://issues.apache.org/jira/browse/SOLR-15361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chris M. Hostetter updated SOLR-15361:
--------------------------------------
    Attachment: SOLR-15361.patch
        Status: Reopened  (was: Reopened)

{quote}I also removed the help info about misleading {{signatory.keyId}} errors 
– Gradle 6.8.3 no longer reports that property name by mistake if 
{{signing.gnupg.keyName}} is unspecified.
{quote}
HA! .. i tricked myself into thinking that because of the error reporting in  
failUnlessGpgKeyProperty ... i've added back that help info with some wording 
tweaks clarifying it means tasks need updated to depend on 
failUnlessGpgKeyProperty to get accurate error msgs.

> update gradle build to support gpg signing of tgz/zip distributions
> -------------------------------------------------------------------
>
>                 Key: SOLR-15361
>                 URL: https://issues.apache.org/jira/browse/SOLR-15361
>             Project: Solr
>          Issue Type: Task
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Chris M. Hostetter
>            Assignee: Chris M. Hostetter
>            Priority: Major
>             Fix For: main (9.0)
>
>         Attachments: SOLR-15361.patch, SOLR-15361.patch, SOLR-15361.patch, 
> SOLR-15361.patch, SOLR-15361.patch, SOLR-15361.patch, SOLR-15361.patch, 
> SOLR-15361.patch, houston.wtf.stderr.txt, houston.wtf.stdout.txt
>
>
> the gradle build does not currently have any support for gpg signing the 
> distributions we produce.
> this is neccessary for releases, and for being able to "smoke test" our 
> Dockerfiles prior to release (by creating mock download servers to confirm 
> {{docker build}} can correctly fetch the {{tgz}} & {{tgz.asc}} files we point 
> it at)



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to