Skip to content

ETCM-165: Fix the 'no pinentry' issue during publishing #964

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Apr 14, 2021
Merged

ETCM-165: Fix the 'no pinentry' issue during publishing #964

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0059081
ETCM-165: Move the gpg step, maybe that's the problem with 'no pinentry'
aakoshh Apr 13, 2021
9e1199c
ETCM-165: Remove publishing on PR branch.
aakoshh Apr 13, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .buildkite/publish.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,9 +18,9 @@ GPG_EXISTS=$(gpg --list-keys "$GPG_KEY_ID" >&2 && echo "yes" || echo "no")

if [[ "$GPG_EXISTS" == "no" ]]; then
echo "$GPG_KEY" | base64 --decode | gpg --batch --import
# Local testing showed that without this the SBT plugin got "Bad passphrase".
gpg --passphrase $GPG_PASSPHRASE --batch --yes -a -b LICENSE
fi
# Local testing showed that without this the SBT plugin got "Bad passphrase".
gpg --passphrase $GPG_PASSPHRASE --batch --yes -a -b LICENSE

# https://github.com/olafurpg/sbt-ci-release#secrets
export PGP_SECRET="$GPG_KEY"
Expand Down