Hi Zbyněk,
This is very great contribution to OpenSCAP community. I like it so much!
It actually helped me yesterday with my pull request.
I also like that it also runs memory leak checking using valgrind.
I have one question: Is it possible to view detailed results of failed tests?
I mean those test logs that our upstream test suite creates in each test directory.
Is it possible to do this using ssh login to a particular Jenkins build?
Regards
Jan Černý
Security Technologies | Red Hat, Inc.
----- Original Message -----
From: "Zbynek Moravec" <zmoravec(a)redhat.com>
To: open-scap-list(a)redhat.com, scap-security-guide(a)lists.fedorahosted.org
Sent: Tuesday, September 22, 2015 8:42:41 AM
Subject: [Open-scap] Public Jenkins infrastructure
Hi contributors,
We have make our Jenkins server public -
https://jenkins.open-scap.org/ (self
signed certificate currently).
Test-machines with Fedora22/RHEL6/RHEL7 are used.
When you push something to your pull requests, Jenkins will automatically
start testing (or ask admin to verification).
White-list for automatic testing currently should contains people which have
ever contributed to OpenSCAP/scap-security-guide.
Tips:
- If you don't want to test your your pull request automatically, you can
add "[skip ci]" phrase to pull request description.
- If you are in admin-list(currently OpenSCAP team in Brno), you can control
jenkins testing by pull-request comments:
- "ok to test" to accept this pull request for testing
- "test this please" for a one time test run
- "add to whitelist" to add the author to the whitelist
If you have any tips/issue with jenkins, feel free to contact me.
Zbynek Moravec
_______________________________________________
Open-scap-list mailing list
Open-scap-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/open-scap-list