Are you ready for Continuous Delivery? Part 2: Feedback loops
This is the second part of a series of posts about Continuous Delivery infrastructure, culture, and process. In this post, we’ll present some of the more common feedback loops your organization should have in place to determine your readiness for Continuous Delivery.
It's not Continuous Delivery if you can't deploy right now.
I hear people say all the time that they're practicing continuous delivery. This declaration is often followed by something like, “I can let the security team know anytime”, or “I just have to run the performance tests”. If you can't push your software to production right now, you're not done with your continuous delivery journey.
Add performance testing to your Continuous Delivery pipeline
Performance testing as part of a Continuous Delivery (CD) pipeline is rare. The intent of this article is to provide you with some pointers on the types of testing you can do on a regular basis, and to give some strategies for implementation.
Vulnerability in GoCD - Java deserialization and Apache commons-collections
This post contains information about a security patch available for GoCD 15.2. If you're using GoCD 15.2 in production, and especially if it is available over the internet, it is highly recommended to apply this patch immediately.
Visibility Is Opportunity: stories of improving continuous integration
Mingle is a 9 years JRuby Rails project. We do test-driven development and continous integration. We write selenium tests to test everything since Oct 2006. For a long time, our build time was 1 to 2 hours. We thought it was a good balance of build time and resources needed...
GoCD is continously improving its plugin infrastructure. Starting 15.2.0, GoCD will support "Plugin Settings" that will allow plugins developers to accept global settings. With this feature all plugins will have one approach to accept plugins settings from user & access plugin settings from GoCD Server.
How to Avoid Brittle Code
The most common problem with legacy code is brittleness. A brittle codebase is one that a team cannot change without great pain. In ThoughtWorks' 10 years of building products we've learned some hard lessons while trying to keep fairly large codebases malleable.
Are you ready for Continuous Delivery?
This is the first part of a series of posts about Continuous Delivery infrastructure, culture, and process. In this first post, we'll present questions you need to answer honestly about your own people, teams, and organization to determine your readiness for Continuous Delivery.
5 Key Deployment Pipeline Patterns
Teams have been automating the build, test and deploy processes of their software for many years, but usually in a very specific "one off" manner. This article walks through 5 key patterns to setting up a successful deployment pipeline, including designing parallel workflows, running tests in parallel, and more.