The reasons to use container platforms, in a modern DevOps project, are to standardize and accelerate software deployments. In this context software pipeline means the technical steps starting from developers change to a repository, application build and Docker container build and finally delivering the tested change to the production on an OpenShift or Kubernetes cluster. We are going to quickly compare the readiness of OpenShift development tools versus the new project Jenkins X. The finding, to highlight here, is that there is no ready made solution that covers every aspect in software pipeline.
One of the biggest reasons to run any project with an Agile approach is to take distance from any form of waste to win time.
A good way to avoid problems with unique servers, is to automate the provisioning and configuration of the environment with a fully automated and script-driven DevOps pipeline.
Some of us had opportunity to attend OpenShift Commons Gathering Helsinki. We wrote a summary of the highlights in this community event.