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.
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
GPG Key import successfully, but "No secret key" when maven deploy #619
Comments
Hello @DQinYuan, Thank for creating this issue and we will look into it :) |
Is there any progress? I'm still waiting for it to release the new version. We can't solve this problem. |
Hi @DQinYuan, The problem you're encountering could be due to the absence of a GPG key in the environment where your action is being executed. Here's how you can fix it: 1.If you haven't done so already, generate a GPG key and export the private key to a file. Execute these commands to accomplish that:
2.Add the data from the private.key file to the secrets of your GitHub repository. |
@gowridurgad I have setted GPG_SECRET 7 months ago I publish package successfully before updating setup-java to v4. |
Hi @DQinYuan, After implementing the process detailed in the previous comment, we no longer observe the error in our logs. I have attached a screenshot for your consideration. Could you please reconfigure the secret by following the steps previously outlined? To verify the existence of the secret, could you please incorporate the following steps into your workflow file?
|
Job with 'Check if secret exists' step. Error because of newline in GPG_SECRET. |
I later troubleshooted and found that the issue was due to an expired GPG key, which was resolved by renewing it. |
Job Url
config:
gpg private key imported successfully:
Bug maven depoly failed with "No secret key":
The text was updated successfully, but these errors were encountered: