Closed hohwille closed 1 year ago
OK, so I fixed this by using a variable with the default value ask
.
Now, for automated build with this Inappropriate ioctl for device
error simply add this to your maven build in github workflow:
-Dgpg.pin.entry.mode=loopback
This way we do not prevent to lockout ourselves in case once an automated release is failing and we have to fallback to a manual release (e.g. via devon release
) but can still reach 100% automation more easily.
Fixed with version 11
. Finally verified.
PR #15 breaks the interactive build:
IMHO for github workflow this workaround is fine but should then be done in a profile. So maybe the easiest solution is that I revert this change and we solve this in a profile with the same ID
deploy
in thesettings.xml
.