Disable debug evidences for Vulnerability Detection E2E tests by default #5331
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MARCOSD4
requested changes
May 7, 2024
juliamagan
approved these changes
May 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Following #4914, the vulnerability detection tests now gather substantial evidence across all test cases. These adjustments were made to address issues in unstable environments. However, the current abundance of evidence may lead to instability during test execution in Jenkins environments. Thus, it is advisable to disable these options by default and refrain from utilizing them when tests are launched automatically.
Testing performed
Build: https://ci.wazuh.info/job/Test_e2e_system/278