Wazuh packages redesign tier 1 - Stage 2 - Migrate and adapt the Wazuhapp

[Tostti]

Description

We are on an effort to modernize the packages' generation and lifecycle. This issue aims to track the effort to migrate the packages' generation process from the wazuh-packages repository and automate its generation, testing and delivery steps of their lifecycle.

The tasks listed below are extracted from https://github.com/wazuh/internal-devel-requests/issues/712. Use that issue for additional information and requirements.

Tasks

• Migrate code into target repository for manual package generation
  • Add dockerized yarn runner #5305
• Automate packages generation through CI
  • Enhance and fix some GitHub actions workflows #4680
  • Enhance Github Actions build process to support multiple plugins #6108
  • Update Build GitHub action #6194
• Automate packages testing through CI
  • Add package test #6508
• Add secrets to GH (to upload packages to S3)
• Upload packages to S3 through CI

[rauldpm]

First estimated ETA provided by @Tostti : 2024/03/22

[rauldpm]

The repository has been configured with CI secrets, please, refer to the main comment of the https://github.com/wazuh/wazuh-jenkins/issues/6290 issue to check the secrets names, the CI used has been configured to put and get objects from the development warehouse

Packages should be uploaded to s3://packages-dev.internal.wazuh.com/development/wazuh/4.x/main/packages/

[rauldpm]

@Tostti after a meeting with @davidjiglesias it has been decided that the plugin files will not be uploaded nor released, you can skip the CI upload task

Secrets removed from the repository

[Tostti]

All steps successfully completed