Test run of Jenkins (CI tool)

Shawn Wells shawn at redhat.com
Wed Sep 3 04:31:00 UTC 2014


Also in the vein of automation, went ahead and installed an instance of
Jenkins and connected it to SSG:

http://jenkins.ssgproject.org:8080/

Not meant to be permanent right now, but wanted to get something stood
up for us to play with. Martin stood one up for the OpenSCAP
interpreter, which was the source of thinking to stand up a sandbox for
SSG too. There really isn't much to see in the UI, but one thing it does
is integrate into GitHub. Whenever someone issues a pull request,
Jenkins will automagically detect that, apply the patch(s), and run
"make validate."

Check out https://github.com/OpenSCAP/scap-security-guide/pull/45 for an
example. Or for the lazy :-), see below:



When you click on Details, you're brought to an overview of the patch
and can even see console output of the build (in case there were errors):
http://jenkins.ssgproject.org:8080/job/scap-security-guide/24/console

Having this in place should afford the peer reviewers an immediate
answer to "does this validate?" Longer term, this could also enable unit
checks of the OVAL and bash scripts.

Does anyone have experience with Jenkins,  thoughts on how we could
begin building out unit tests, or really any thoughts on usefulness
beyond "make validate" on pull requests?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fedorahosted.org/pipermail/scap-security-guide/attachments/20140903/5b6106e9/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bbhcaeee.png
Type: image/png
Size: 78286 bytes
Desc: not available
URL: <https://lists.fedorahosted.org/pipermail/scap-security-guide/attachments/20140903/5b6106e9/attachment-0001.png>


More information about the scap-security-guide mailing list