Repository navigation
ci: skip work that passed with the same files, and shard the end-to-end tests by state - #77
Merged
Merged
Conversation
… the runner ci/plan.py keys each unit by the blobs it depends on and the week, and a unit that passed leaves a marker in the cache under its key. Pull requests run the shards that apply the role only for changes to the role, the tests or the Rust code that feeds it; main runs them for any change. The Rust jobs restore main's target directory and set unchanged files to an old time (ci/mtimes.py), so cargo rebuilds only what changed.
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.
CI ran every check and every playbook run on each push, about 12.5 minutes even for a docs change.
ci/plan.pygives each unit (Rust tests, clippy, Python tests, each e2e shard) a key from the files it reads and the week. A unit that passed leaves a marker in the cache, and a run with the same key skips it. A pull request sees its own markers and main's.SHARDSintests/e2e/run.py). On a pull request the shards that apply the role run only for changes to the role, the plugins, the tests or the Rust code inSEAM; main runs them for any change.ansible_contractpins the variables berth hands the role, so a change elsewhere that alters them shows up and runs them.ci/mtimes.py), so cargo rebuilds only what changed. Only main saves those caches.A run started by hand on the branch, with no cache, took 7m43s. All nine shards also passed locally on fresh hosts with the same test counts as before.