Thanks Antonie, Yes, that's what we did.
For ref: [ https://wiki.archlinux.org/index.php/GnuPG#Unattended_passphrase, https://bbs.archlinux.org/viewtopic.php?pid=1479136 https://www.gnupg.org/documentation/manuals/gnupg/GPG-Esoteric-Options.html#GPG-Esoteric-Options ] It was a tough nut to crack with the intension of having the build and release done from buildr witin a docker container. On Mon, Mar 12, 2018 at 11:44 PM, Antoine Toulme <anto...@toulme.name> wrote: > Just browsing through here: https://www.gnupg.org/ > documentation/manuals/gnupg/GPG-Configuration.html <https://www.gnupg.org/ > documentation/manuals/gnupg/GPG-Configuration.html> > > Squinting hard at the doc, it looks like you’d like to be able to write > gpg.conf under ~/.gnupg with your options. > > > > On Mar 12, 2018, at 11:10 AM, Antoine Toulme <anto...@toulme.name> > wrote: > > > > No, the current code doesn’t seem to allow passing additional options > when issuing the command line arguments. > > > > There might be a way to use environment variables? What additional > parameters do you need? > > > >> On Mar 11, 2018, at 12:25 AM, Sathwik B P <sath...@apache.org> wrote: > >> > >> Hi, > >> > >> GPG signing artifacts will not work in non interative mode with GPG > 2.1. It > >> still asks for the passphrase even when the passphrase is provided with > the > >> gpg --passphrase command. > >> > >> One option to make this work non interactively is to add "pinentry-mode" > >> loopback in the gpg.conf. > >> There are other recommendations in gpg forum. > >> > >> Is there a way to pass additional options to the gpg? > >> [https://github.com/apache/buildr/blob/master/addon/buildr/gpg.rb] > >> > >> regards, > >> sathwik > > > >
