THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
There are 2 ways to configure your GPG key for release, either using release automation script(which is recommended), or running all commands manually. If using Mac, please see below to handle known issues.
Use preparation_before_release.sh to setup GPG
...
- Configure git to use this key when signing code by giving it your key ID, as follows:
git config --global user.signingkey CD4C59FD, or git config --global user.signingkey 623E08E06DB376684FB9599A3F5953147903948A
- You may drop the --global option if you’d prefer to use this key for the current repository only.
- Start GPG agent in order to unlock your GPG key
eval $(gpg-agent --daemon --no-grab --write-env-file $HOME/.gpg-agent-info)
export GPG_TTY=$(tty)
export GPG_AGENT_INFO
If using Mac you might encounter these issues with the not time setup
- apt-get is not available . So install gpg using https://gpgtools.org/
- Create gpg key with your apache emailId and publish to key server
- The KEYS file is in https://dist.apache.org/repos/dist/. The checkout you would need subversion
If subversion is not available in Mac you might have to first install it using `brew install subversion`.
Access to Apache Nexus repository
...