If you’re working with software, you’ve probably come across the terms “Continuous Delivery,” “Pipeline Runners,” and “Infrastructure as Code (IaC).” Or perhaps you’re already benefiting from automated deployments in your organization and want to learn more about the inner workings of these magic boxes.
Subscribe
Get our best content on how to build better apps.
Subscribe
Get our best content on how to build better apps.
Got product development questions?
Join us on
Discord
Certified Kubernetes Admin Exam Survival Guide [from a CKA]
If you’ve found this guide, odds are you’re considering taking the CKA exam, or you’ve already been preparing and are looking for final review material. Regardless of which position you find yourself in, here is some advice on how to approach the CKA exam in ways that aren’t included in the excellent killer.sh exams.
Dylan Lundquist
How to Deploy Storybook to GitHub Pages with GitHub Actions
If you’re using GitHub Actions as your Pipeline Runner, Bitovi has created a new GitHub action that makes publishing your Storybook to GitHub Pages a snap. It’s using a new feature in GitHub pages to help keep your repositories clean.
Mick McGrath
DevOps Consulting: Pipeline Runners
Pipeline Runners, and the automation pipelines they run, simplify software delivery by providing a hosted mechanism to automate running tests, building packages and artifacts, and performing deployments. In other words, Pipeline Runners run Pipelines, which are the foundation of your Automated Delivery process and your overall DevOps or Cloud Engineering approach.
Mick McGrath
It's Time to Rethink How We Version Artifacts
We have been versioning products for ages. Some products use a basic numbering scheme starting at one and incrementing the changes. Other products, such as cars, use the year to indicate a version. A version is “A particular form of something differing in certain respects from an earlier form or other forms of the same type of thing.”
Chris Capell
Cloud Ready Series: Setting up a CI Pipeline
Continuous Integration (CI) is the process of automating the stages of testing, building, and publishing. It is considered one of the first steps toward creating a truly automated end-to-end deployment process. The aim of CI is to create an artifact that can be deployed into one or more systems, preferably with a Continuous Deployment (CD) pipeline.
Phil Henning