My project rolls the latest updates to the stack on EL6 to ensure that we
can discover any drift or bugs in the OpenSCAP stack prior to release.
It would be great to be able to continue to do this on all supported OSs
without needing to spin up additional hosts for the building process.
We also do this to allow users that have created in-house additions and/or
modifications to the Guide to evaluate their systems easily.
Since, as far as I know, you have to modify the Guide to do this I'm not
sure what options this leaves folks that are required to remain on EL6
until end of Phase 2 support.
On Tue, Feb 26, 2019 at 11:08 AM Matěj Týč <matyc(a)redhat.com> wrote:
the possibility to build the ComplianceAsCode/content project on RHEL6
using python2.6 and other dated utilities is becoming a luxury. It
prevents contributors to use elegant constructs available in python2.7,
and sometimes passing the CI for RHEL6 requires some weird workarounds
that take time to design and implement and those workarounds just
complicate the code, they don't bring benefits.
As RHEL6 won't get any significant updates and one can build RHEL6
content on other OSs (or in a container), the RHEL6 CI setup seems to
gain negative value. Do you, our precious community around the project,
have arguments why the RHEL6 should be part of the CI?
If there are no agreed-upon reasons, we are leaning towards switching
the RHEL6 CI off within two weeks, i.e. in the first half of March.
On behalf of the Brno Security Compliance team,
scap-security-guide mailing list --
To unsubscribe send an email to
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
Vice President, Onyx Point, Inc
(410) 541-6699 x788
-- This account not approved for unencrypted proprietary information --