CI/CD pipelines have become increasingly prevalent as a way way to approach software promotion workflows, because of their promise of full automation. The desired outcome of a well designed CI/CD pipeline is confidence in the software delivery process so that releases can be done at any time. And in fact a deployment in production becomes a non-event.
Very few companies have reached this nirvana, in part because old processes are difficult to change and CI/CD techniques and technologies are relatively new and not completely established. This leaves many open questions. What are the mandatory steps of a well designed pipeline? What type of control and verifications steps should we have? How do we implement compliance and auditing? What is the right technology stack? Who owns the pipeline?
In the OpenShift arena, I have addressed some of the design questions in these two blog posts: Cross-Cluster Image Promotion Techniques and Environment-Dependent Property Management Strategies for OpenShift Pipelines.
At this year’s Red Hat Summit on Wednesday, May 3, I’ll host an interactive session discovery session that addresses use cases gleaned from the audience. Attendees will walk away with their questions answered and an understanding of how to create container-driven continuous delivery that works for the organization.
Connect with Red Hat Services
Learn more about Red Hat Consulting
Learn more about Red Hat Training
Learn more about Red Hat Certification
Subscribe to the Training Newsletter
Follow Red Hat Services on Twitter
Follow Red Hat Open Innovation Labs on Twitter
Like Red Hat Services on Facebook
Watch Red Hat Training videos on YouTube
Follow Red Hat Certified Professionals on LinkedIn