----- Original Message -----
> From: "Shawn Wells" <shawn@redhat.com>
> To: "scap-security-guide" <scap-security-guide@lists.fedorahosted.org>
> Sent: Wednesday, September 3, 2014 6:31:00 AM
> Subject: Test run of Jenkins (CI tool)
>
> 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."
I wanted to create a testing Jenkins instance for all things OpenSCAP.
There are fixed costs in maintaining the master and all the slaves.
You have to take care of the machines, keep them updated, etc... You
have to keep updating Jenkins itself and be on top of plugin updates.
In my opinion it makes no sense to have 2 Jenkins servers for projects
so closely related. I would prefer to pool resources.
Unfortunately we can't just host our Jenkins on OpenShift because we need
multiple slaves for RHEL 5, 6, 7 and Fedora. And the storage space available
is not enough for our use-case.
> Check out https://github.com/OpenSCAP/scap-security-guide/pull/45 for an
> example. Or for the lazy :-), see below:
The integration is really cool. I planned to make the Jenkins instance
public after a testing period and do exactly this.