geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (GEODE-3199) geode-examples on the release branch prompts for a gpg password
Date Wed, 20 Sep 2017 17:50:00 GMT


ASF subversion and git services commented on GEODE-3199:

Commit 5d034de588a43cdefb8fbb3a6259579785768340 in geode-examples's branch refs/heads/develop
from [~upthewaterspout]
[;h=5d034de ]

GEODE-3199: Make signing with a gpg key optional

Make it optional to sign the archives with a gpg key, to avoid annoying
users trying to build the examples. You must specify the property
-PsignArchives to sign with a gpg key.

(cherry picked from commit 76cce858773dd390c27de717a5d7c92a9d7aaf9b)

> geode-examples on the release branch prompts for a gpg password
> ---------------------------------------------------------------
>                 Key: GEODE-3199
>                 URL:
>             Project: Geode
>          Issue Type: Bug
>          Components: build
>            Reporter: Dan Smith
>             Fix For: 1.3.0, 1.2.1
> When building geode-examples using ./gradlew build from the release/1.2.0 branch, I get
prompted to enter my gpg password. Since our instructions on running the examples tell the
user to run gradlew build, they will hit this prompt when building the released examples.
> Travis is also showing this failure:
> {noformat}
> You must configure your signing.keyId and signing.secretKeyRingFile
> in ~/.gradle/ in order to sign jars
> See
> FAILURE: Build failed with an exception.
> {noformat}

This message was sent by Atlassian JIRA

View raw message