OpenShift automates the process of building new container images for all of your users. OpenShift can run standard docker builds based on the dockerfiles you provide. OpenShift also provides a “source-to-image” feature which allows you to specify the source from which to generate your images. This allows administrators to control a set of base or “builder images” and then users can layer on top of. The build source could be a GIT location, if you want OpenShift to build your application container images from source. It could also be a binary like a WAR/JAR file, if you want us to integrate with your existing application build process. Users can also customize the build process and create their own S2I images.
OpenShift automated the deployment of application containers. It supports rolling deployments for multi-containers apps and allows you to roll back to an older version. Users can also customize their deployments to enable blue green, A/B and canary style deployments.
OpenShift provides built-on continuous integration capabilities with Jenkins and can also tie into your existing CI solutions, whether that’s Jenkins, Bamboo, TeamCity, or anything else. OpenShift’s Jenkins image can be used to run your Jenkins masters and slaves, or you can leverage it just for slave builds in OpenShift and integrate it with your existing Jenkins masters.