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-1226) Release process should not require putting passwords in plain text files
Date Fri, 15 Apr 2016 03:08:25 GMT


ASF subversion and git services commented on GEODE-1226:

Commit 3fd1eec9114b2c72bb620578e118bceba8ea89a7 in incubator-geode's branch refs/heads/feature/GEODE-17-2
from [~upthewaterspout]
[;h=3fd1eec ]

GEODE-1226: Prompt for a password to sign and upload to maven

The signArchives and uploadArchives tasks require passwords to work.
Adding a flag to request a password prompt to fill in a password.

./gradlew uploadArchives -Paskpass

This will pop up a swing dialog box asking for passwords to sign and
upload archives.

This is not on by default because we don't want developers to have to
enter a password for every build. The build target depends on
signArchives but normally will skip it if the password property is not

> Release process should not require putting passwords in plain text files
> ------------------------------------------------------------------------
>                 Key: GEODE-1226
>                 URL:
>             Project: Geode
>          Issue Type: Task
>            Reporter: Dan Smith
>            Assignee: Dan Smith
>             Fix For: 1.0.0-incubating.M3
> Our current release steps require putting your apache password and gpg keyring password
in a plain text file. 
> {noformat}
> signing.password=YourSuperSecretPassphrase      # Plaintext passphrase to decrypt key
> nexusPassword=password                          # Your password on Apache's LDAP 
> {noformat}
> We should change the build to prompt for a password if required.

This message was sent by Atlassian JIRA

View raw message