| Summary: | [RFE] Integration with ResultsDB | ||
|---|---|---|---|
| Product: | [Community] rpm-test-trigger | Reporter: | Jon Orris <jorris> |
| Component: | general | Assignee: | beaker-dev-list |
| Status: | NEW --- | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | unreleased | CC: | jhutar, jorris |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | Bug | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | 1371750 | ||
| Bug Blocks: | 652429, 1351482 | ||
|
Description
Jon Orris
2016-12-12 19:02:36 UTC
ResultsDB v1.0 allows PASSED, INFO, FAILED, ERROR, WAIVED, NEEDS_INSPECTION, v2.0 only allows PASSED, FAILED, INFO, NEEDS_INSPECTION but it is possible to add "note" and any number of "key=values" to the result. I assume we will stick to v2.0. (In reply to Jan Hutař from comment #3) Might be off-topic for this bz, but I would suggest *not* to embed the name "rpm-test-trigger" in the test case name stored in ResultsDB. After all, rpm-test-trigger is just the thing *triggering* the test, it has nothing to do with the test that is actually being executed (which is really rpmdeplint and its various checks). You might reasonably imagine a future (not so distant) where someone insists that the tests be triggered in Jenkins instead of a standalone daemon. At which point rpm-test-trigger would not be needed. I see. Makes perfect sense. Removing needinfo for myself, since I'm not involved in Beaker/rpmdeplint, and I don't know anything about future plans for ResultsDB. |