Repository navigation
ci: route pushes to main by what they changed - #91
Merged
Merged
Conversation
Every push to main ran the full suite, so a README change booted four VMs and loaded rules into six kernels. A push is now routed by the files it changed, like a PR. Every merge is a squash of a PR that already ran those tests. - A push to main diffs the commit before it with the new one. A scheduled run, a manual run, and a push with no known earlier commit run everything. - The integration and lint workflows also run weekly and by hand, so the full suite still runs when nothing was pushed. - A workflow file selects only the tests it runs. Only changes.yml and the routing script select the full suite. - .gitignore and the ruleset files select nothing, config/wazuh selects lint, Bats and packaging, and tests/lint.sh selects lint. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Contributor
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
This file contains hidden or 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
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.
Summary: a push to
mainnow runs only the tests for the files it changed, like a PR does. Until now every push tomainran the full suite, so a README change booted four VMs and loaded rules into six kernels.Changes
changes.ymldiffs the commit before the push with the new one and routes it throughscripts/dev/ci-changes.bash. Every merge is a squash of a PR that already ran those tests.integration.ymlselects the kernel, VM and container jobs. Onlychanges.ymland the routing script select the full suite..gitignoreand the ruleset files select nothing. They ran the full suite before.config/wazuh/selects lint, Bats and packaging.tests/lint.shselects lint.ADR 0021 said that pushes to
mainrun the full suite, so it has a dated note.What still runs the kernel, VM and container jobs
Changes to
scripts/(outsidescripts/dev/),rules/*.rules,config/auditd/,tests/ci/,integration.yml, and any shell, AWK, rule or conf file elsewhere.Tested
tests/bats/ci-changes.batshas two new tests for the new rules. This PR changeschanges.yml, so it runs the full suite itself.