brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rdowner <>
Subject [GitHub] incubator-brooklyn pull request: More fixes to release blockers
Date Fri, 26 Jun 2015 09:52:37 GMT
GitHub user rdowner opened a pull request:

    More fixes to release blockers


You can merge this pull request into a Git repository by running:

    $ git pull more-fixes-to-release-blockers

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #720
commit ee2ff728c5d6fe8baea640e6204a2a1420085795
Author: Richard Downer <>
Date:   2015-06-25T15:39:49Z

    Update pom.xml GnuPG settings
    Sets the executable to gpg2, which is the usual name for the latest gpg
    versions both on Linux and MacPorts.
    Removes the set-empty-passphrase property. With gpg-agent correctly set
    up, this means that the signing process will prompt for the GPG
    passphrase when it is first needed, and cache the value for the
    remainder of the build. This is more secure than writing down a GPG
    passphrase either in settings.xml, pom.xml, or anywhere where it might
    up in a command line history file.
    Setting up gpg-agent in 10 seconds:
    - Install a pinentry package. pinentry-mac from MacPorts;
      pinentry-curses if you are remoting into a Linux machine
    - Install gpg-agent if not already installed (on Ubuntu you'll need to
      apt-get install gnupg-agent; but on MacPorts it's part of the gnupg2
    - Start the agent:
      - gpg-agent --daemon --write-env-file "${HOME}/.gpg-agent-info"
      - GPG_TTY=$(tty)
      - export GPG_AGENT_INFO GPG_TTY

commit 80a51203ba6dfa47dfa62a1fd2d6d66775358944
Author: Richard Downer <>
Date:   2015-06-26T09:11:10Z

    Mark an intermittently-failing test as WIP


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message