Metasite Business Solutions, Lithuania
— TOPIC —
Exclude Human – Continuous Deployment and OpenShift
There were times when software deployment took days and a bunch of software engineers worked on a release with an aim to successfully deliver features and meet specific timelines. Today, the situation may easily be different as we’ve got all the tools we need, however we’re still afraid of Continuous Deployment. We know we can do it, but are we?
The times have changed – we’re living in the world of automation, therefore Human is no longer a viable option for repetitive tasks. Should a Human still check if development and deployment are well configured, if an API is responding well, if we’ve introduced a regression? These and similar cases nowadays may easily be tackled by writing a test or adding some quality gate to our deployment pipelines. The best part, of course, is what we can do with Continuous Deployment – do not be afraid of failures because we can react swiftly.
This talk is about Continuous Deployment with OpenShift, how it fits the Reactive Manifesto and how those who enjoy software writing may achieve their goals in a more efficient way. No matter if you’re an enterprise giant, a local e-shop owner or a geek who’s all into building APIs – the right tooling and a comprehensive strategy allow for a great automation. Here’s what we’ll cover:
- Git strategy: dos and don’ts
- Pipelines in Jenkins
- Pipeline stages, minimum quality gates
- What about the Data?
- What about confidential information, secrets, tokens, passwords?