This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/plc4x-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 67c8196b4 Site checkin for project PLC4X: Jenkins Tools
67c8196b4 is described below
commit 67c8196b487051416f7c1df1e5724dc96a37ccf4
Author: jenkins <[email protected]>
AuthorDate: Fri Jun 30 13:57:17 2023 +0000
Site checkin for project PLC4X: Jenkins Tools
---
developers/release/release.html | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/developers/release/release.html b/developers/release/release.html
index 6a09a36d9..dbe84684f 100644
--- a/developers/release/release.html
+++ b/developers/release/release.html
@@ -446,6 +446,21 @@ However, in contrast to that documentation, upload your
key to the following ser
<div class="paragraph">
<p>Ideally use the Maven-Wrapper to ensure the Maven version fits the
build.</p>
</div>
+<div class="admonitionblock note">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-note" title="Note"></i>
+</td>
+<td class="content">
+On some systems (mainly Mac) gpg signing can result in errors like:
+ <code><code>[INFO] --- maven-gpg-plugin:3.0.1:sign
(sign-release-artifacts) @ plc4x-parent ---
+ gpg: signing failed: Inappropriate ioctl for device</code></code>
+ In this case adding the following helps: <code>export GPG_TTY=$(tty)</code>
+</td>
+</tr>
+</table>
+</div>
</div>
<div class="sect2">
<h3 id="preparing_the_codebase_for_a_release">Preparing the codebase for a
release</h3>
