Setup MSI Build Workflow for Windows

[vikman90]

Parent Issue:

• Develop GitHub Actions Workflows for Building Wazuh Agent Packages #129

Description

This issue involves creating a GitHub Actions workflow to automate the building of MSI packages for the Wazuh agent on Windows. The workflow will target amd64 architecture, ensuring compatibility with Windows Server 2008 R2 and above.

Requirements

• Configure GitHub Actions to build MSI packages for Windows (amd64).
• Set up the environment using tools such as WiX Toolset to generate the installer.
• Ensure the MSI installer properly registers the Wazuh agent as a Windows Service.
• Ensure the workflow generates .msi files and stores them as artifacts for download.

Tasks

• Create a GitHub Actions workflow YAML file for the MSI build process.
• Install required dependencies such as WiX Toolset for creating MSI installers.
• Implement steps to build an MSI installer for the Wazuh agent.
• Store the generated .msi file as an artifact in Amazon S3.
• 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.

[jotacarma90]

Update 10/01/2025

• I start working on the general wazuh-agent-packages workflow for the MSI generation.
• I am making the necessary changes to the current 4.X script, packages-build-windows-agent.yml.
• We tried to split the compile, package generation and test steps into three different jobs, to end up creating actions for each task, in order to be able to use the same compile files for several different jobs.
• I have almost adapted the workflow to start testing, pending to create PR.

Update 13/01/2025

• I have created PR to upload the first changes made to the workflow: https://github.com/wazuh/wazuh-agent-packages/pull/180
• Testing and mini-fixes solution.
• Gathering all the necessary changes that I will ask DevOps to add to the Windows machine.

Update 14/01/2025

• Created issue request to add new dependencies to allocator Windows machine: https://github.com/wazuh/wazuh-automation/issues/2048
• Continue testing a solving minor issues in the workflow.
• ETA delayed due to extended fixing with dependencies and VM problems.

Update 15/01/2025

• I have been working together with DevOps to test the Windows machine with all its dependencies.
• Modifying the workflow to adapt it to these changes.
• Troubleshooting the compiling and formatting of the workflow.
• Investigating a bug related to the setting of the AUTOMATION_BRANCH variable in the start allocator action.
• Investigating problems booting the Windows machine, issue open: https://github.com/wazuh/wazuh-automation/issues/2053#top

Update 16/01/2025

• Found the problem with the automation branch in the start allocator action: https://github.com/orgs/community/discussions/25240
• Fixed multiple errors in workflow execution.
• We have finished preparing and checking the Windows machine of the allocator.
• Added binary caching functionality to the Windows compilation script.
• Added the check install, upload steps and finished the last details of the workflow.

Update 17/01/2025

• Workflow working correctly: https://github.com/wazuh/wazuh-agent-packages/actions/runs/12825887172/job/35764742446
• We have created an auxiliary branch where to enter all changes related to splitting the workflow into multiple jobs for the use of the compiled build in multiple places: enhancement/139-windows-package-workflow-different-jobs
• Latest revisions and adjustments made.
• Due to some extra problems encountered, the separation of functionalities in jobs, and some complications with the allocator machine, we need to expand the ETA a couple of days more to finalize everything correctly.

Update 20/01/2025

• Solving last problems related to workflow steps, inputs and different usages.
• Testing package created.
• Fixing branch enhancement/139-windows-package-workflow-different-jobs
• Workflow 🟢: https://github.com/wazuh/wazuh-agent-packages/actions/runs/12869850862