Skip to content
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

Setup RPM Build Workflow for Wazuh Agent #136

Closed
3 of 6 tasks
Tracked by #129
vikman90 opened this issue Sep 11, 2024 · 1 comment · Fixed by #261
Closed
3 of 6 tasks
Tracked by #129

Setup RPM Build Workflow for Wazuh Agent #136

vikman90 opened this issue Sep 11, 2024 · 1 comment · Fixed by #261
Assignees
Labels
level/subtask Subtask issue type/enhancement Enhancement issue

Comments

@vikman90
Copy link
Member

vikman90 commented Sep 11, 2024

Parent Issue:

Description

This issue focuses on creating a GitHub Actions workflow to automate the building of RPM packages for the Wazuh agent on CentOS 7 or a similar RHEL-based distribution. The workflow will target amd64 and aarch64 architectures, ensuring that the Wazuh agent can be consistently built and distributed for these platforms.

Requirements

  • Configure GitHub Actions to build RPM packages on CentOS 7.
  • Set up the build environment by installing necessary dependencies such as rpm-build and mock.
  • Build the Wazuh agent targeting amd64 and aarch64.
  • Ensure the workflow generates .rpm files and stores them as artifacts for download.

Tasks

  • Create a GitHub Actions workflow YAML file for the RPM build process.
  • Install dependencies for RPM package creation.
  • Implement steps to build Wazuh agent RPMs for both target architectures.
  • Verify that the RPMs are built correctly and stored in the proper AWS S3 bucket.
  • Configure the workflows to trigger automatically on GitHub events like pull requests or merges to the main branch.
  • Include a manual trigger option for rebuilding the packages on-demand.
@mjcr99
Copy link
Member

mjcr99 commented Oct 28, 2024

Update

(28/10/2024) Updated docker images upload workflow to make it capable of managing the new 5.0.0 images. The new images are being uploaded.
(29/10/2024) Found problems related to RAM consumption while building the package dependencies. Implement a mechanism to let the package-building procedure use our remote binary caching repository to build the package faster and avoid RAM problems.
(30/10/2024) Still having problems related to job getting killed, investigating solutions. The VCPKG_MAX_CONCURRENCY has been tested with no success.
(31/10/2024) Problem related to jobs getting killed has been solved. Working on a solution to use the remote binary caching and use the RPM installed version which can not detect the installed packages in the package testing step.
(04/11/2024) Remote binary caching finally working for packages building. Moved mono installation to Dockerfiles. Set RPM version to 4.15.1 in RPM Dockerfile to avoid problems with the RPM db has seen here:

(05/11/2024) Updated workflow file to manage different upload options. Improved packages' building code by cleaning it and removing deprecated options.
(06/11/2024) Cleaned additional deprecated options and improved dependencies binary caching.

@wazuhci wazuhci moved this from Backlog to In progress in XDR+SIEM/Release 5.0.0 Oct 28, 2024
@vikman90 vikman90 removed the mvp label Oct 29, 2024
@wazuhci wazuhci moved this from In progress to Pending review in XDR+SIEM/Release 5.0.0 Nov 7, 2024
@wazuhci wazuhci moved this from Pending review to In review in XDR+SIEM/Release 5.0.0 Nov 7, 2024
@wazuhci wazuhci moved this from In review to In final review in XDR+SIEM/Release 5.0.0 Nov 8, 2024
@wazuhci wazuhci moved this from In final review to Done in XDR+SIEM/Release 5.0.0 Nov 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
level/subtask Subtask issue type/enhancement Enhancement issue
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants