Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Gitlabs integrated CI vs OpenShift, the Slant community recommends Gitlabs integrated CI for most people. In the question“What are the best continuous deployment Kubernetes platforms?” Gitlabs integrated CI is ranked 7th while OpenShift is ranked 8th.
Specs
Question Ranking
Pros
Pro CI is integrated into the version control system
Pro Open-source
Pro Easiest CI for Windows binary, because of Docker-Windows Runner Executor
Pro Small learning curve
Learning to use OpenShift is pretty easy. Most environments can be set up in a few simple steps and for everything else the official documentation and third-party resources are extremely helpful.
Pro Built-in continuous integration
Continuous integration is not only built-in OpenShift, it's actually a standard part the workflow.
Pro Can be used to introduce specialized tasks through the application hosted on it
Because of its high flexibility and customization power, OpenShift can be used to create specialized tasks for the application being hosted on it. For example, an entire array of dynos (also known as gears) can be dedicated to media transcoding in order to build a custom media converter infrastructure.
Cons
Con Security risks
Con Only works with gitlab
Con Not lightweight
Not a lightweight solution, demanding and memory hungry.
Con No Windows support
No Windows support, but it's possible to use a Bitnami stack.
Con Official customer support is lacking
OpenShift seems to rely more on written documentation and on the community to solve any problem users may have. The forums and IRC channel are active and very helpful, but the official customer support could be better.
