config: Run only fluster-debian Jobs on media-committers tree #1075
+70
−2
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
This patch creates a separate KBuild Job for media-committers tree to exclude it from the base "kbuild-gcc-12-arm64-chromebook" kernel build one. Duplicated base KBuild Job will run only for media-committers tree and will trigger only fluster-debian tests. Other tests could create noise when verifying media-committers changes. Scheduler entries had to be duplicated to use the new triggering event. Signed-off-by: Paweł Wieczorek <pawiecz@collabora.com>
|
Tested on staging |
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.
This patch creates a separate KBuild Job for media-committers tree to exclude it from the base "kbuild-gcc-12-arm64-chromebook" kernel build one.
Duplicated base KBuild Job will run only for media-committers tree and will trigger only fluster-debian tests. Other tests could create noise when verifying media-committers changes.
Scheduler entries had to be duplicated to use the new triggering event.