Tar error in the package build workflow

[rauldpm]

Description

• Inputs
  • architecture: x86_64
  • checksum: false
  • is_stage: true
  • reference_security_plugins: 4.9.0
  • reference_wazuh_plugins: 4.9.0
  • revision: 999
  • system: rpm
  • CHECKOUT_TO: 4.9.0

The package name revision for the base file seems to be not correct (see revision)

It has been possible to see the following error too:

This error appears to be related to the security plugin

Extracting Security application
tar: stdout: write error

We need to check if those errors are related or not, also, the workflow finished as a success, but it should not

Related

• https://github.com/wazuh/wazuh-dashboard/actions/runs/8705493002
• https://github.com/wazuh/wazuh-dashboard/actions/runs/8707714490
• https://github.com/wazuh/wazuh-dashboard/actions/runs/8708343547
• https://github.com/wazuh/wazuh-dashboard/actions/runs/8708349023

[Tostti]

Research

The issue seems to be related to a large output from a command in the GitHub Actions.
It happens due to the line

 directory_name=$(tar -tzf wazuh-dashboard.tar.gz | head -1 | sed 's#/.*##' | sort -u)

Used in the base generaction script to get the name of the subfolder of the Dashboard package regardless of the version and how was it constructed.
Will research about an alternative way to do this that avoids this error. However it does not cause any problem in the package generation itself, and the generated packages works as expected.

[Tostti]

Update 17/4

To resolve the issue, a workaround was implemented: instead of retrieving all the compressed package content to get the subfolder name, we get the last folder created in the directory after extracting the package

directory_name=$(ls -t | head -1)

This was implemented in three different sections on which this problem was present.

Additionally, it was noticed that the building process didn't stop if a plugin failed to install. New logic was added to detect those events and end the script execution in that case.

[Tostti]

I'm reopening the issue because due to the branch changes for compatibility with 2.13, the workflow is showning some new errors