Someone throw me an example of using it in Travis CI, under Docker, with access to repo updates and another example of using it via Vagrant in GitLab.com and I'm totally in.
I gave up trying to figure out a way to do it without putting my developer key in places where it doesn't look like I can put my developer key. Now, If I'm allowed to put my developer key in a Git repo and let it fly to the four winds without getting in trouble, that's really easy! Otherwise, someone needs to hop on one of the 80 places that RedHat has technical blogs and clue me in.
Alternatively, giving FOSS projects free runners in a Red Hat cloud that has access to repo updates would work.
Heck, AppVeyor even lets me test on Windows easily (as does Vagrant in many cases) but trying to test on RHEL in a public CI system is more work than it's worth.
In terms of the flow down, I'm not using this for validation on any sort of real system and am making no claims that it means anything. What I'm doing is using what the rest of the FOSS world uses to develop and doing something that lets me know if there are going to be absolutely catastrophic effects when I test on RHEL without needing to figure out how to get developer keys working in GitLab and/or Travis.