Continuous Integration
Like nails on a chalkboard: ‘We haven’t shipped’
Recently, the Hertz car rental company sued Accenture for $32M in damages. The suit (pdf) alleges breach of contract in Accenture’s agreement to build and deliver a new website. This new site was supposed to: support the Hertz, Thrifty, and Dollar brands, starting with Hertz, North America be a ‘responsive’ site that works across phone,
Delivering Secrets to Applications, Securely
I synthesized and expanded what I’ve been sharing about delivering secrets to applications into a 1 hour talk and presented it at the Phoenix DevOps meetup on Wednesday. This talk covers (Recording (YouTube), Slides (Google)): the fundamental challenges of handling secrets, including The First Secret Problem common ways you can lose control of them in
Controlling Access to Secrets within CI/CD Systems
Controlling access to secrets within Continuous Integration and Delivery (CI/CD) systems is very important. CI/CD those systems often use credentials with highly-privileged access to create and publish business critical artifacts and application deployments. This post shares pointers for how to protect access to secrets in Jenkins, Gitlab Enterprise, CircleCI, and CodeFresh.
APIs are the ante for the Cloud service game
If a service can’t be provisioned and managed via an API, it’s not a Cloud service.
Good release artifacts drop onto deployment platforms
This deep-dive on Continuous Integration started with saying that a project’s CI process should build the canonical release artifacts for a project or product. These release artifacts should archive the application that was built along along with application-specific tools such as scripts required to run the application. Avg Reading Time: 3 minutes These artifacts will
Continuous Integration of a Containerized Application
Learn how to create a continuous integration process that packages custom software into a Docker image, tests, and publishes that as a releasable artifact.
Continuous Integration for Infrastructure Code
Continuous Integration can and should be applied to infrastructure code written in tools like Terraform and CloudFormation. This post describes how.
What does Continuous Integration look like in 2019?
The primary goal of a continuous integration process is to provide rapid feedback on changes to the development team. Teams use CI to determine whether a change is reasonable to deploy for further testing.
Improving Software Delivery Performance with Continuous Integration and Continuous Delivery
Much of the extra effort and delay in software delivery processes is hiding in long-lived feature branches and test environments built from long-lived release branches. Deliver more frequent releases with lower lead times using Continuous Integration and Delivery (CI/CD).