-
Notifications
You must be signed in to change notification settings - Fork 206
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add job group filter options for /tests/overview #5388
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #5388 +/- ##
=======================================
Coverage 98.36% 98.36%
=======================================
Files 389 389
Lines 37454 37490 +36
=======================================
+ Hits 36840 36876 +36
Misses 614 614 ☔ View full report in Codecov by Sentry. |
<%= help_popover('Help for the <em>Include job group</em> filter' => ' | ||
<p>Shows jobs from job groups matching these globs</p>') %> | ||
<input name="group_glob" type="text" id="group-glob" | ||
placeholder="globs, comma separated, e.g. *kernel*,*Tumbleweed*" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The default globs are not very creative, there's probably better ones to show. 🤔
While i've only really used the zero or more character syntax in tests, there's other options as well: https://metacpan.org/pod/Text::Glob#SYNTAX |
This change introduces Text::Glob as a new dependency. Because globs are much safer for user provided input than regular expressions, which are prone to ReDoS attacks. Progress: https://progress.opensuse.org/issues/134933
aabf9da
to
1505a6a
Compare
Based on #5388, and reusing most of the same logic, to bring job group filtering to `/tests` from `/tests/overview`. Similar to the `?match=...` option, this does not have a UI element yet and can only be used by manually entering the query parameter. Since the question of how to extend the filter form with text fields is still open, i consider it out of scope for this PR. Progress: https://progress.opensuse.org/issues/134933
Based on #5388, and reusing most of the same logic, to bring job group filtering to `/tests` from `/tests/overview`. Similar to the `?match=...` option, this does not have a UI element yet and can only be used by manually entering the query parameter. Since the question of how to extend the filter form with text fields is still open, i consider it out of scope for this PR. Progress: https://progress.opensuse.org/issues/134933
This is a followup for #5388 and #5401. When there were no matches for job group globs, no query condition would be generated previously. Giving the false impression that all job groups were matching. So now we just generate an impossible query that cannot match anything with the group id `0`. Progress: https://progress.opensuse.org/issues/134933
This is a followup for #5388 and #5401. When there were no matches for job group globs, no query condition would be generated previously. Giving the false impression that all job groups were matching. So now we just generate an impossible query that cannot match anything with the group id `0`. Progress: https://progress.opensuse.org/issues/134933
This change introduces Text::Glob as a new dependency. Because globs are much safer for user provided input than regular expressions, which are prone to ReDoS attacks.
Progress: https://progress.opensuse.org/issues/134933