-
Notifications
You must be signed in to change notification settings - Fork 21
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
Research the necessary migration from wazuh-packages to Agent repository #30
Comments
Update(09/07/2024) Reviewing migrated code and its requirements. (10/07/2024) Migration requirements analysis:
(11/07/2024) Reviewed @MarcelKemp feedback, additional conclusions: Regarding /wazuh-packages/.github/workflows packages generation workflows, there is a testing mechanism that has not been implemented in the migration and we may consider it. In the wazuh-packages repository, every time a change took place in a packages generation related file, testing packages were created to verify the changes did not break the structure and let the code ready to keep building packages with the new changes. As long as it should not be mandatory to migrate this mechanism, we should consider implementing it, keeping in mind our new structure, as a good CI practice. |
Review
|
ReviewWorkflows:These are workflows to simply test the installation of the generated packages on an array of OSes from different distributions and architectures that support the package:
This check to install the package is already done in the same workflow, although it is tested only on the same machine used to generate the package:
|
Conclusion
Update July 15
|
Description
The code related to the Wazuh agent package generation must be migrated from the repository
wazuh-packages
to its new repository, this issue aims to analyze and document what must be migrated.Tasks
wazuh-packages
repository for agent package-related codeThe text was updated successfully, but these errors were encountered: