Re: [ee4j-build] how to access staged artifacts?

[Mark Thomas <markt@xxxxxxxxxx>]

On 30/10/18 22:42, Bill Shannon wrote:
> Ok, I guess it's time to submit a ticket.

You can work around it.

I created a Jenkins job that did:

#!/bin/sh -ex

# Need GPG public key so dump it here
gpg --batch --import ${KEYRING}
gpg --armor --export

and then I manually uploaded the public key to one of the key servers
that the failed job said it was looking in.

Mark


> 
> Romain Grécourt wrote on 10/30/2018 03:29 PM:
>> It fails to validate your GPG key. The GPG key needs to be published
>> to a valid GPG server.
>> See https://central.sonatype.org/pages/working-with-pgp-signatures.html#distributing-your-public-key
>>
>> This should be a one time thing, whoever owns the key should have done
>> that. 
>>
>> On Tue, Oct 30, 2018 at 3:16 PM Bill Shannon <bill.shannon@xxxxxxxxxx
>> <mailto:bill.shannon@xxxxxxxxxx>> wrote:
>>
>>     Ok, I'm getting further, I think.
>>
>>     The upload seems to have succeeded:
>>
>>     [INFO] Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/jakartaactivation-1020/com/sun/activation/jakarta.activation/1.2.1/jakarta.activation-1.2.1.pom.asc (833 B at 8.4 kB/s)
>>     [INFO]  * Upload of locally staged artifacts finished.
>>     [INFO] Remote staged 2 repositories, finished with success.
>>
>>
>>     Then it fails with this when I try to close the repository:
>>
>>     [ERROR] 
>>     [ERROR] Nexus Staging Rules Failure Report
>>     [ERROR] ==================================
>>     [ERROR] 
>>     [ERROR] Repository "jakartaactivation-1020" failures
>>     [ERROR]   Rule "signature-staging" failures
>>     [ERROR]     * No public key: Key with id: (d908a43fb7ec07ac) was not able to be located on &lt;a href=http://keys.gnupg.net:11371/&gt;http://keys.gnupg.net:11371/&lt;/a&gt;
>>     <http://keys.gnupg.net:11371/%3Ehttp://keys.gnupg.net:11371/%3C/a%3E>. Upload your public key and try the operation again.
>>
>>     and lots more errors like that.
>>
>>     Is that because I don't have permission to publish to that groupId?
>>
>>     Or is it because of some other security/gpg problem?
>>
>>     Did it fail to sign my artifacts?  I don't get any errors from
>>     maven-gpg-plugin.
>>
> 
> 
> 
> _______________________________________________
> ee4j-build mailing list
> ee4j-build@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/ee4j-build
>