ableegoldman commented on a change in pull request #10203:
URL: https://github.com/apache/kafka/pull/10203#discussion_r592825616
##########
File path: README.md
##########
@@ -69,10 +69,6 @@ Generate coverage for a single module, i.e.:
### Building a binary release gzipped tar ball ###
./gradlew clean releaseTarGz
-The above command will fail if you haven't set up the signing key. To bypass
signing the artifact, you can run:
-
- ./gradlew clean releaseTarGz -x signArchives
Review comment:
Yes, we're suddenly seeing our soak test applications which deploys from
trunk fail with
```
./gradlew clean install releaseTarGz
> Configure project :
Building project 'core' with Scala version 2.13.5
Building project 'streams-scala' with Scala version 2.13.5
> Task :connect:signMavenJavaPublication FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':connect:signMavenJavaPublication'.
> Cannot perform signing task ':connect:signMavenJavaPublication' because it
has no configured signatory
```
I personally haven't been able to reproduce this, but both @wcarlson5 and
@lct45 have reported running into this issue
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
