| Summary: | Increase the amount of standard tasks | ||
|---|---|---|---|
| Product: | [Retired] Beaker | Reporter: | Roman Joost <rjoost> |
| Component: | Doc | Assignee: | beaker-dev-list |
| Status: | CLOSED WONTFIX | QA Contact: | tools-bugs <tools-bugs> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | develop | CC: | mjia |
| Target Milestone: | --- | Keywords: | FutureFeature |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | Triaged | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-10-21 14:13:24 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
Nick had an excellent proposal to find possible candidates of tasks we could move upstream: > there could be some interesting metrics to be retrieved from the Beaker task library, like: > > - last execution date > - last successful execution date > - total number of executions > - all time pass/fail rate > - "recent" executions > - "recent" pass/fail rate > - total number of different users > > The practical purpose of that would be to look for the ones which are executed a lot by a lot of different people, as those would be strong candidates for migration to the upstream Beaker project as standard tasks.