-
Notifications
You must be signed in to change notification settings - Fork 94
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
Fix and improve bump proccedure in wazuh-packages repository #2243
Comments
UpdateCreated script that modifies the necessary files in the repository to bump to a new version:
Additionally, we have created a GitHub Action that can be used to automatically launch the script and open a PR with the changes. To execute the action go to the actions tab and look for the workflow named Then click on Here we can see a test execution of the workflow: And the resulting pull request: To DoAdd keys to sign the commits done in the GH action |
UpdateAdded GPG keys to sign commits with the GitHub action and added the necessary steps to the workflow. We have encountered an issue where GnuPG returns the following error when signing the commit:
We are currently investigating the error. |
Removing ETA as we're prioritizing other issues. |
UpdateLocated the cause of the signing problem, it seems that the GH actions machine does not have tty causing the signing process to fail. |
Removing ETA as we're prioritizing other issues. |
UpdateAfter reviewing some related issue from different repositories: We have found that the cause of the error in signing the commits seems to be related to the GPG version used to generate the GPG key. As a possible solution, different sources recommend generating a key without a password or generating a key using GPG1. |
To be done as part of: wazuh/wazuh-qa#4820 |
The current automatic bump procedure in Jenkins has some issues with the current structure of the SPECS directories and with the unattended installer, we need to fix it and improve it if possible.
Proposed solution
The text was updated successfully, but these errors were encountered: