MarcelKemp
commented
7 months ago Update 15/04
After being able to resume this issue (due to other higher priority issues), I have investigated the checks that are run for dashboard and indexer, and I am making the necessary changes to both wazuh-packages and wazuh-jenkins to prevent them from running:
- PR packages: https://github.com/wazuh/wazuh-packages/pull/2909
- Jenkins: investigating to try not to remove the checks that simply install the manager.
Update 16/04
PRs ready for review:
rauldpm
Description
Due to the redesign of packages, and their corresponding migration, carried out in the following issue:
It is intended to prevent checks related to the dashboard and indexer from failing due to lack of updates. Because from
4.9.0onwards, maintenance, and upgrades will be done in their own repositories.To avoid failed checks, we want to prevent them from being triggered when the base branch is 4.9.0 or higher, so we will have to remove these checks from the GHA workflows, as well as from the CI checks executed in Jenkins, so that they are not executed again for these versions.
Failed checks to avoid
Unattended install + Distributed cases
These checks are executed from Jenkins within the Wazuh CI group, so it is necessary to apply the necessary settings in the wazuh-jenkins repository to prevent the execution of these checks. It seems that the files related to the triggers is the following:
Password tool script tests
This other case, when executing also the unattended install script, it is necessary that it is not executed either, as it will fail as the previous ones. In order not to execute it, it is simply necessary to delete the triggers (
on pull request) that are in the workflow: