-
Notifications
You must be signed in to change notification settings - Fork 9
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
jobs/bodhi-trigger: add reporting to ResultsDB #50
Conversation
It's funny to still have it say 'Running' even when it's done.
Prep for reporting, which will use code from cosa.
Requires coreos/coreos-assembler#3656. |
string(name: 'OVERRIDES', value: msg.update.url), | ||
]) | ||
} | ||
cosaPod(cpu: "0.1", kvm: false) { |
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.
0.1 CPU enough?
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.
Yeah, should be plenty. We're just triggering a job and doing two HTTP POSTs essentially. :)
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.
LGTM
Call out to the new `resultsdb-report` script in cosa to report test results back to ResultsDB. Report when first running and then again with final test results. Just this alone seems sufficient for the results to show up in Bodhi's "Automated Tests" tab. With this, we'll then be able to work on adding policies in Greenwave.
I just removed some extra braces. Merging! |
Call out to the new
resultsdb-report
script in cosa to report testresults back to ResultsDB. Report when first running and then again with
final test results.
Just this alone seems sufficient for the results to show up in Bodhi's
"Automated Tests" tab.
With this, we'll then be able to work on adding policies in Greenwave.