Hi,

On behalf of oVirt's CI team, I'm happy to announce the STDCI build summary
-
*We've used patternfly *[1] <http://www.patternfly.org/> to ensure a clean,
simple and elegant view of information for your builds.
The summary is available for STDCI V2 [2] projects and it is located under
*build-artifacts/ci_build_summary.html*


*[image: location.png]*


STDCI build summary is a single web page, generated dynamically for every
build on STDCI.
It visualizes all CI threads that ran for that build and features a set of
quick links.

The main view shows a list of all threads with an indicator if that thread
failed or passed.
The quick links to the right of each thread lead to *log* and *artifacts*
of that thread only.
Note that *log* shows the output of your script only to ease debugging.
[image: threads_list.png]

At the top right side, you will find a set of quick links for convenience:

[image: menus.png]

*Test results* (available if JUnit XML files were exported during the
build) leads to a summary of all JUnit test results that were collected
during the build.
*Test results analyzer *shows the history of test execution results in a
tabular format.
*Findbugs results *(available if Findbugs report was generated and exported
during the build) shows trend report for Findbugs.
*Full build log* shows the full log of all threads. This log is harder to
understand as it includes output from CI runtime environment as well as
from your scripts.

*Rebuild (for GitHub PR)/Retrigger (for Gerrit patch): *Run the build
again. The new build will report and vote to Gerrit/GitHub with the new
result.
*View PR/patch: *Links back to the PR on GitHub or patchset page in Gerrit.


[image: view_in_jenkins.png]
*View in Jenkins* will lead you back to the build view in Jenkins

[image: view_in_blueocean.png]
*View in Blue Ocean *will lead you to the build view in Jenkins Blue Ocean
view

STDCI Documentation
https://ovirt-infra-docs.readthedocs.io/en/latest/CI/Build_and_test_standards/index.html

For any questions, don't hesitate to contact the CI team at #rhev-integ,
#rhev-dev
or view mail at [email protected].

Thanks,
Daniel.
_______________________________________________
Devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/[email protected]/message/XCRLR7XPCYBOMDT5MGBYHHI4FKO3427C/

Reply via email to