[Open-scap] Public Jenkins infrastructure

Šimon Lukašík isimluk at fedoraproject.org
Tue Sep 22 09:25:48 UTC 2015


On 09/22/2015 10:13 AM, Zbynek Moravec wrote:
> Hi,
>
> - Yes, unfortunately we cannot run every pull request with valgrind, because it takes hours.
>
> - SSH - You can use ssh to connect to the build using https://wiki.brq.redhat.com/SecurityTechnologies/OpenSCAP/jenkins,

There is nothing secret (like passwords) on this page. Thus, I think we 
should migrate this whole page to open-scap.org website. That would be a 
bit more visible than a blog post.

Anyway, thanks Zbyňek for this effort. I feel the effects of this change 
every day!

Thanks!
~š.

> but it currently allowed only for Brno OpenSCAP team. Anyone can ask for the access (but we don't want to allow
> unknown people to access to machine due to possible security issues ). I am going to write blogpost about it.
> (I have already started, but I am not the fastest writer.)
>
> - Tests results - Jenkins should be discussed on meeting today and we will talk also about form of results.
>
> Zbynek Moravec
>
> ----- Original Message -----
>> From: "Jan Cerny" <jcerny at redhat.com>
>> To: "Zbynek Moravec" <zmoravec at redhat.com>
>> Cc: open-scap-list at redhat.com, scap-security-guide at lists.fedorahosted.org
>> Sent: Tuesday, September 22, 2015 9:46:00 AM
>> Subject: Re: [Open-scap] Public Jenkins infrastructure
>>
>> 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 at redhat.com>
>>> To: open-scap-list at redhat.com, scap-security-guide at 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
>>>


More information about the scap-security-guide mailing list