> What makes it a PaaS is that it integrates Jenkins
Not just Jenkins. There is a Jenkins button and you can use Jenkins for CI/CD, but you can define BuildConfig and ImageStream through their point-and-click interface without ever adding Jenkins or writing a line of config by hand.
You just need to use one of their built-in ImageStreams and DeploymentConfigs. I got my first exposure to OpenShift through the Developer Preview/OpenShift Console beta. At the time I was testing it out, deployment of Jenkins was outright broken, but I was able to get my app working and builds automatically generated in response to GitHub webhooks (eg, CD without Jenkins.)
The Developer Preview was a very interesting experience, and their support people were quite responsive in #openshift-dev, but I'm giving them some latitude in that it was clearly labeled as Preview / Beta and a totally free product with built-in expiration date.
I would not have been likely to call it a good experience except that it was clearly labeled beta. But if it says Beta on the tin, and I am able to complain until it works, that's about where I set the bar for good experience. It was a good beta experience.
If I had to guess, OpenShift.io is the next phase of this:
https://console.preview.openshift.com/console/
(I am certain that you will not need to use OpenShift.io online IDE to get "batteries included" OpenShift from RedHat.)