-
Notifications
You must be signed in to change notification settings - Fork 197
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Query greenwave by critical path group when possible
When possible - i.e. when the critpath.type implementation provides grouped information, i.e. when it's "json" - this makes Bodhi query greenwave for a different context for each critical path group an update contains package(s) from. The intent is to allow us to run and gate on different sets of tests for different critical path groups. For instance, if an update is only in the critical path for Server, it doesn't make much sense to run and gate on GNOME/Workstation-related tests. If an update is only in the critical path for LXDE, maybe we don't need to run or gate on any tests at all (as we don't have any for LXDE). This should only be deployed in production after the Fedora greenwave policy has been updated to contain a policy for each critical path group defined in `critpath.py`. A risk of this approach is that we will actually hit an exception if we wind up querying for a context that has no policies. It may be possible to use wildcards in the 'null' policy to defend against this, I will check. We update a lot of related tests to use this codepath rather than the old one as we may, in future, want to drop the old codepath and only support this one. But we keep one test on the old codepath to make sure it works. Signed-off-by: Adam Williamson <awilliam@redhat.com>
- Loading branch information
1 parent
29504a6
commit e09a7d5
Showing
4 changed files
with
128 additions
and
19 deletions.
There are no files selected for viewing
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 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 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 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